Skip to content

Latest commit

 

History

History
48 lines (43 loc) · 2.99 KB

RPIP-43.md

File metadata and controls

48 lines (43 loc) · 2.99 KB
Raw
rpip title description author discussions-to status type category created requires tags
43
Megapools
A single contract per node operator that can be used as an Ethereum withdrawal address for multiple validators. Also allows for ETH-only node operation.
Valdorff (@Valdorff)
TBD
Draft
Protocol
Core
2024-03-05
eip-4788
tokenomics-2024, tokenomics-content

Abstract

This proposal drastically reduces the gas to add validators and distribute rewards for them. It does so by creating a single contract that can be used as the Ethereum withdrawal address for any number of validators. In addition, the contract will facilitate the application of node-level penalties, as opposed to the current state where penalties are assigned and processed at the minipool level. Note that this proposal also enables ETH-only Node operation.

Specification

  • A Node Operator SHALL be able to deploy a single megapool contract
    • This MAY be combined with the deposit of their first validator
  • A Node Operator SHALL be able to add a validator to their existing megapool contract
  • A Node Operator SHALL be able to exit one or more validators in their megapool contract
  • A Node Operator SHALL be able to distribute rewards from all validators in their megapool at once
    • This MAY be temporarily blocked while validators are exiting
  • Legacy minipool deposits (ie, deposits not in megapools) SHALL be disabled
  • RPL MAY be staked to a megapool
    • Validators MAY be created within a megapool regardless of RPL staked to the megapool (note that this means ETH-only node operation is possible)
  • Legacy RPL staking (ie staking RPL to a node rather than to a megapool) SHALL be disabled
  • A user MAY set any amount of RPL "Staked" to a megapool to "Unstaking"
  • Once RPL has been "Unstaking" for unstaking_period days, it can be withdrawn (this setting is defined in RPIP-30)
  • All RPL that was "Unstaking" MUST be withdrawn at one time
  • There SHALL only be a single time stored for "Unstaking" RPL; this means that if a user sets additional RPL to "Unstaking" after some RPL is already "Unstaking", they must wait for unstaking_period before any is available to withdraw
    • All RPL that was already "Unstaking" for unstaking_period SHOULD be withdrawn when a user sets additional RPL to "Unstaking"

Vote Eligibility

  • All nodes are eligible to receive vote power.
  • For nodes eligible to receive vote power, total RPL staked (to either a megapool or the node) SHALL contribute to vote power up to 150% of the value of total bonded ETH (from both megapools and legacy minipools).
    • Note that "Unstaking" RPL SHALL NOT be counted
    • If this RPIP is ratified, a note SHALL be added to the "Eligibility" section of RPIP-4 saying that it has been superseded by this section

Reference Implementation

See https://github.com/rocket-pool/rocketpool-research/blob/master/Megapools/megapools.md

Copyright

Copyright and related rights waived via CC0.