RPIP-44: Integrating Execution Layer Triggerable Exits Source

Describes when EL triggerable exits will be used within RP
⚠️ This RPIP is not recommended for general use or implementation as it is likely to change.
RPIP44
AuthorValdorff, Mike Leach
StatusDraft
TypeProtocol
CategoryCore
Requires eip-7002
Created2024-03-05
DiscussionLink

Contents

RPIP-44: Integrating Execution Layer Triggerable Exits Source

Describes when EL triggerable exits will be used within RP

Abstract

This proposal specifies when execution layer triggerable exits as defined in EIP-7002 will be used by RP contracts. There are two enumertated use cases. The first is that the Node operator may freely request exits of their validators. The second is a keeper mechanism that allows and incentives any user to forcibly exit a Node Operator's validators if that Node Operator owes the protocol a threshold amount. This helps keep rETH performant and minimizes funds lost to theft.

There is an additional use case that is not addressed in this RPIP, which is to exit badly-performing (eg, abandoned) validators. It is likely the pDAO will wish to supersede this RPIP in order to include that functionality. However, as it requires modeling and is not a critical function to the work in RPIP-49, it is not being addressed at this time. For similar reasons, this RPIP does not include a keeper-bsed design to reward those that trigger forced exits. Please see a historical version of RPIP-44 for initial but incomplete ideas to address abandonment and a keeper network.

Specification

  • An exit function SHALL be included in the Megapool delegate
    • This function SHALL take in an array of validator public keys
    • This function MAY be freely called by the Node Operator
    • This function MAY be called by any user if the Node has a deficit greater than exit_deficit
      • It MUST NOT be possible to exit more than the minimum number of validators needed to cover deficit
  • debt is incurred via penalties, as enumerated in RPIP-42
  • The protocol SHALL use rewards and/or credit held by the NO to decrease debt by the same amount prior to taking action on exits
  • The protocol SHOULD use staked RPL held by the NO to decrease debt by the corresponding amount prior to taking action on exits
  • The initial settings SHALL be:
    • exit_deficit: 0.2 ETH

Copyright and related rights waived via CC0.

Citation

Valdorff, Mike Leach, "RPIP-44: Integrating Execution Layer Triggerable Exits [DRAFT]," Rocket Pool Improvement Proposals, no. 44, March 2024. [Online serial]. Available: https://rpips.rocketpool.net/RPIPs/rpip-44.