Stake ETH on behalf of node (RPIP-32)

RPIP-32 lets an independent address fund an RP node with ETH. The node can use this ETH to make minipools, without having direct access to the ETH.

Outcome if vote passes

RPIP-32 will be implemented in a future smart contract release Once implemented, it supports a variety of situations were the node operator is not directly providing the ETH.

Rationale

This supports a variety of situations were the node operator is not directly providing the ETH:

• Enhanced security for node operators, as they can stake directly from their hardware wallet, eliminating the need to transfer funds to the node beforehand
• Staking as a Service providers where custody of funds are managed by a trusted custodian
• Protocol integrations where custody of funds are managed by smart contracts
• DAOs or organisations where custody of funds are managed by a treasury

While the primary aim of this feature is to facilitate single depositor scenarios, it's worth noting that multiple independent depositors can also leverage this capability by creating smart contracts layered on top.

Context

Full RPIP Forum thread