All Core Devs - Consensus (ACDC) #181, June 25 2026

Agenda

Devnet updates:

Other topics:

  • Builder API — remove submitBeaconBlock (builder-specs#162). Revisit now that devnet-6 is about to launch with builder integration. (bharath-123)
  • Builder API — circuit breakers — @bharath-123: should we specify clients MUST fallback to self-build with impl-dependent heuristics (like Bellatrix)? Standardize or leave flexible?
  • FYI Staked Builder API (builder-specs#138) has been merged.
  • Proposer Preferences API — remaining concerns on beacon-APIs#608? (james-prysm)
  • Has anyone reviewed this? Beacon API #618 validator state renaming — breaking change; pending-queued states outdated post-EIP-6110/7251. Ecosystem tooling impact assessed? (leobago, barnabasbusa)
  • (feat: extend /eth/v1/node/peers with peer scoring and disconnect reasons)[Beacon API #606] — requested by @barnabasbusa. Status?

Glamsterdam:

  • EIP-8080 DFI — let exits use consolidation queue. Intent to DFI stated in PQ Interop #15. Any remaining blockers?
  • EIP-8045 SFI — exclude slashed validators from proposing. Was CFI→SFI in #179. Potuz to open Prysm PR — status? Can we SFI now?
  • EIP-8282 — builder execution requests. @nflaig requested discussion at #180. DoS attack surface vs. impl cost tradeoff assessed? Builder deposit limit risk revisited?

Hegota:

  • Hegota non-headliner window — opened after EL headliner decision. End date still TBD based on Glamsterdam progress.

Meeting Time: Thursday, June 25, 2026 at 14:00 UTC (90 minutes)

GitHub Issue

1 Like

Video, transcript & chatlog

News coverage

Resources

Meeting Summary:

The meeting focused on updates and discussions regarding DevNet 5 and 6, with Barnabas reporting that DevNet 5 has been stable for three weeks despite some range syncing issues in Lighthouse and Prism clients. The team discussed moving forward with DevNet 6, which launched shortly before the meeting, featuring most EIPs except stable containers and including three execution layer clients. The group reviewed several API and builder-related changes including the State Builder API for Glamstadam, Beacon API PRs, and peer scoring extensions, with clients agreeing to provide reviews by ACDT for merging these updates. A significant portion of the meeting centered on the go/no-go decision for EIP-7688 (progressive containers), where client teams provided mixed responses with three saying yes and three saying maybe, leading to the decision to include it in DevNet 7 rather than the current fork. The team also discussed EIP-8080 (exit queue consolidation) and decided to move it to DFI status for future implementation in Higota, while updates were shared on A2A2 builder execution requests and contract adjustments.

Click to expand detailed summary

The team discussed updates on DevNet 5 and 6, with Barnabas reporting that DevNet 5 has been stable for three weeks, though some clients like Lighthouse and Prism experienced range syncing and peering issues. DevNet 6 was launched and includes most EIPs except stable containers, with three execution clients currently onboarded. The team confirmed plans to test slashing validators pre-fork and addressed a potential spec bug (Gloas attestations with `data.index == 1` are always considered to fail payload matching · Issue #5399 · ethereum/consensus-specs · GitHub) that will be fixed for DevNet 7. Regarding circuit breakers, the team agreed to maintain a client-specific approach rather than standardizing them, as no clients have implemented them yet and there was uncertainty about their readiness for mainnet deployment.

The team discussed circuit breakers for MEV boost, with Terrence explaining that Prism uses a simple implementation based on missed blocks and epochs, though they identified a need to incorporate payload status rather than just beacon blocks. Terrence reported progress on the State Builder API for Glamstadam, including multiplexing support for different builders, though this implementation needs to be merged into the main branch before full testing. The group also reviewed several API-related pull requests, including the Beacon API Proposal Preferences and peers API extensions with peer scoring, with plans to merge these changes by ACDT pending client approvals.

The team discussed a new proposer path PR for APIs that includes Get Block V4 and Submit Block APIs for Glamsterdam, which James had already approved. Barnabas emphasized the need for immediate testing, while Parithosh suggested reviewing and merging the PRs by ACDT to prepare for DevNet 7. James noted that the PR author, Shane, is out of office until July 4th, so the team needs to act quickly for any changes. Barnabas announced he would block Dora page for devnet 6 until Beacon API PRs are merged.

The team discussed whether to include EIP-7688 (progressive containers) in DevNet 7. Most clients reported being close to implementation readiness, with some expressing concerns about the invasive nature of the changes required. The group decided to target inclusion in DevNet 7, pending stability of DevNet 6, with the option to revisit if the implementation proves too challenging. Three clients confirmed they could implement it, while three were uncertain, resulting in an overall positive but cautious alignment toward inclusion in the next devnet.

The team discussed EIP-8080, which aims to address a gap in the consolidation specification by allowing faster exits when the exit queue is clogged. Dima explained that this could help level the playing field between different staking providers, while concerns were raised about implementation complexity. The group decided to move EIP-8080 to DFI status, with the authors planning to re-propose it for a future Higota release. They also confirmed that EIP-8045, which prevents exit validators from proposing, is already implemented in DevNet 5 and ready for SFI status.

The team discussed updates to contract logic and constants for the Glamsterdam upgrade, with Marius reporting that Felix implemented a new version that updates fees when someone is added to the queue rather than on every block. Nico proposed reducing deposit constants from 32/256 to 8/64 to improve builder UX by reducing withdrawability delay. The team agreed to wait for the contract changes to be finalized before proceeding with external audits, with Kevaundray suggesting end of July post-devnet 7 as a timeline. Justin Florentine requested guidance on creating CL-level specs for the Lucid project, and Loring announced a 3 ETH bounty from Shutter and the Encrypt the Mempool Coalition for feedback on draft EIPs 8105 and 8184.

Next Steps:

  • Barnabas: Add clients to DevNet 6 as soon as they are ready to be onboarded.
  • Parithosh: Patch the spec bug raised by Michael and target the next DevNet (DevNet 7) for the spec release.
  • Terence: Update Prism’s circuit breaker implementation to consider payload status instead of beacon blocks.
  • Terence: Merge the Builder API multiplexing features into the main branch for use in the next DevNet.
  • Client Teams: Review and provide approvals for the Beacon API PR (GLUAS Proposal Preferences API) by ACDT.
  • Client Teams: Review and provide approvals for the PR extending the peers API with peer scoring and disconnect reasons by ACDT.
  • Client Teams: Review the new proposer path PR (Get Block V4 and submit block all) and leave comments or approvals by ACDT.
  • Client Teams: Review the simplify payload attributes event PR and aim to merge by ACDT for inclusion in DevNet 7.
  • Client Teams: Target EIP-7688 for inclusion in DevNet 7, with the understanding that it may be deferred if it proves too complex.
  • EIP-8080 Authors: Re-propose EIP-8080 for the Higota non-headliner window.
  • Nico/Marius/Felix/Matt: Signal when the A2A2 builder execution request contract is in its final state for audit.
  • PK910: Open a PR to discuss the dynamic queuing size for the A2A2 contract.
  • Justin Traglia: Reach out to Justin Florentine to provide guidance on CL-level specs for Lucid.

Recording Access:

YouTube Stream Links: