All Core Devs - Consensus (ACDC) call #137, July 11 2024


Consensus-layer Call 137 · Issue #1096 · ethereum/pm · GitHub

Moderator: @ralexstokes


ACDC #137 recap by @ralexstokes (from Eth R&D Discord)
Shorter call today!

We began with Pectra:

  • CL clients are generally ready for pectra-devnet-1
  • CL clients working well with static test vectors
  • Given a few EL clients are ready, we should launch pectra-devnet-1 as soon as possible, aiming for sometime next week

Then, turned to PeerDAS:

  • peerdas-devnet-1 launched but surfaced a number of client bugs which are being resolved
  • Expect a peerdas-devnet-2 soon as client teams continue to iterate on scaling blob bandwidth
  • I gave an update on the work to uncouple the blob max and target values between the consensus and execution layers
    • After reviewing the syncing semantics, it appears the check for the blob maximum on the EL is redundant and we can safely drop that check and have it done solely at the CL
    • We also want the same uncoupling treatment for the blob target so this value will be driven by the CL but needs to be included in the EL block header for the security of client sync
    • Expect updates to this PR on the CL and an EIP for the 4844 changes soon™!

Wrapped the call with an update on some work to expand the fork choice testing

  • Presentation from TXRX research here: FC compliance test suite on ACDC - Google Slides
  • This work introduces tooling to expand the scope of the fork choice test suite for static coverage in clients
  • Uses a constraint-driven programming language to generate interesting test cases which extend the static test corpus CL clients use for conformance testing
  • CTA: CL teams please take a look and incorporate into your client for enhanced coverage

See you next time!



[To be added]

Additional info

Notes by @Christine_dkim: Ethereum All Core Developers Consensus Call #137 Writeup | Galaxy