This page reproduces proposal text and published results preserved from Snapshot. It reflects the archive capture below.
Archive capture completed:
Published voting information
State at capture
closed
Voting type
basic
Created
2023-12-06 22:43:38 UTC
Voting opened
2023-12-06 22:43:37 UTC
Voting closed
2023-12-20 22:43:37 UTC
Snapshot block
18730318
Participation score
11884.651187417325
Published quorum
7432.3182
Quorum type
default
Recorded ballots
252
Published choice scores
Choice
Score
For
10468.668065396374
Against
0
Abstain
1415.983122020948
Preserved proposal text
Original text, including Markdown notation. Linked content is not reproduced here.
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](https://rpips.rocketpool.net/RPIPs/RPIP-32)
[Forum thread](https://dao.rocketpool.net/t/rpip-32-stake-eth-on-behalf-of-node/2252)