All Core Devs - Execution (ACDE) #207

Protocol Calls & happenings
,
1

ACDE#207

Agenda

Facilitator email: tim.beiko@ethereum.org

GitHub Issue

1 Like
2

Action Items & Next Steps

  • Hoodi will launch on 17/03 as a new long-lived testnet, with a short-term focus towards testing validator exits. It will activate Pectra on 26/03.
  • A mainnet fork time for Pectra will only be chosen after Pectra successfully activates on Hoodi and client teams feel confident in the state of testing. Mainnet will be scheduled at least 30 days after the Hoodi fork (April 25 or later).
  • Fusaka Planning Timelines
    • March 24: deadline for EIPs to be Proposed for Inclusion in Fusaka
    • March 31: deadline for client teams to share their preferences about scope
    • April 10: Fusaka scope frozen

Summary

Pectra

  • We discussed potential post-Holesky path forwards and agreed to “Plan A”: launching a new testnet.
    • This will enable us to test validator exists, which is impossible on Holesky right now given the exit queue will take ~1 year to empty.
    • All other Pectra functionality, including validator consolidations, can still be tested on Holesky and Sepolia.
    • This option was chosen to avoid client teams writing custom code to clear the Holesky exit queue (“Plan D”), which could lead to further bugs and delay work on Pectra fixes and Fusaka implementations.
  • Hoodi will launch next Monday March 17 and activate the Pectra network upgrade on Wednesday March 26.
    • The network will have the same configuration settings as mainnet, and a similar validator count.
  • Staking operators and infrastructure providers who must test Pectra validator exists should deploy to Hoodi ASAP.
  • Once Pectra successfully activates on Hoodi, a mainnet fork time for Pectra will be chosen. This will be at least 30 days after the Hoodi fork, but potentially farther out if infrastructure providers need more time to test on Hoodi.
  • In parallel to this, client teams will continue testing the various Pectra features across Holesky, Sepolia and the various test suites. Specific test scenarios include:

Fusaka

  • Agreement to move forward with Felix’s suggestions to add proofs to transaction payloads.
  • Fusaka Planning Timelines
    • March 24: deadline for EIPs to be Proposed for Inclusion in Fusaka
    • March 31: deadline for client teams to share their preferences about scope, including which EIPs they think should be Declined for Inclusion.
    • April 10: Fusaka scope frozen
  • We could not review two proposed EIPs (PAY opcode and EIP-7819) on the call directly. While we will try and make space for them on subsequent ACD calls, champions are encouraged to provide materials that can be reviewed async and/or in breakout rooms.

Other Topics

1 Like
3

Audio

Writeups

4