Try   HackMD

Max EB Meeting Agenda

Link to current most updated max EB spec

The case for MaxEB in electra

  • currently 977k active validators - we don’t have testing beyond 1.6 million
  • we bought ourselves time with EIP-7514 but this was a bandaid, we must use the time we bought
  • re-staking is just around the corner and we have no idea how much additional demand that could generate for staking
  • MAX_PER_EPOCH_ACTIVATION_CHURN_LIMIT allows us to hit 1.6 million validators in 1 year
  • the longer we wait to implement this, the less impact it will have on the overall validator set size
  • if the number of validators becomes a problem, our only other option is adjusting the issuance curve which is extremely contentious
  • an ounce of prevention is worth a pound of cure
  • seems to be a strong desire for this from the community
  • hardly any complexity on the Execution Layer given that they've already agreed to implement EIP-7002
  • my initial read on this from Lighthouse is that it's not too difficult

Remaining decisions to make in the spec

How do we handle changing to COMPOUNDING_WITHDRAWAL_PREFIX?

How do we stuff blocks with SignedConsolidation's?

  • Require a block proposal / off-chain solution from staking pools
  • Gossip a beacon operation (more complex)

Max EB vs Inclusion Lists

  • Does the Prysm team still feel like MaxEB is too complex to put into Electra?
  • Would it be too ambitious to do both?

Edge cases to consider

  • Double stuffing SignedConsolidations in blocks
  • Creating validators with 0x02 credentials before the fork