Glamsterdam Devnet-2 Advances as Devs Finalizes CFI Scope

Ethereum developers finalize Glamsterdam CFI at ACDT #66 as Devnet-2 advances, EIP-8037 ships as-is, & MEV-Boost remains external to clients.

Glamsterdam Devnet-2 Advances as Devs Finalizes CFI Scope

Ethereum core developers made meaningful progress on the Glamsterdam upgrade during All Core Devs Testing (ACDT) Call #66, finalizing its CFI scope, advancing execution layer devnets, & clarifying the roadmap for ePBS & MEV-Boost discussions.

The meeting, facilitated by Parithosh, focused on stabilizing Devnet-2, reviewing execution layer EIPs already in scope, & resolving lingering inclusion debates that could impact Glamsterdam’s final composition.

BALs Devnet-1 Stabilizes

Developers confirmed that BALs Devnet-1 has reached a stable state after resolving sync issues across most clients. The devnet has been running reliably with EVM fuzzing in place, while parallel IO & execution testing were intentionally excluded from this phase.

With the environment now considered stable, benchmarking responsibilities have been formally shifted to Devnet-2, marking a clear handoff to the next stage of the testing process.

BALs Devnet-2 Scope Locked

The scope for BALs Devnet-2 is now clearly defined & limited to proposals considered mature enough for near-term testing. Included items:

  • EIP-7843
  • EIP-7778
  • Pre-refund gas accounting alignment
  • Receipt updates introducing a second field (already spec’d)
  • EIP-7708 (PRs actively merging)
  • EIP-8024 included without recent changes

Open design discussions tied to these proposals have been deferred to ACD & Devnet-3. PRs are expected to merge quickly, with Devnet-2 targeting rollout this week, although some clients may join slightly later.

ePBS Testing Progress

Work on enshrined Proposer-Builder Separation (ePBS) continues to advance, with teams increasingly focused on preparing the system for coordinated testing. Specifications have now been frozen for test vectors, and block processing implementations are nearing completion across multiple clients, clearing the way for testing to begin in the near term.

However, overall client readiness remains uneven, as several implementations are still missing critical components such as block production logic, gossip validation, and storage handling, highlighting the need for further alignment before broader devnet participation.

EIP-8037 Decision & CFI Finalization

One of the most consequential outcomes of ACDT #66 was the resolution of the EIP-8037 debate. After extended discussion on whether to simplify or delay the proposal, developer sentiment leaned toward shipping the current design, contingent on the availability of adequate tooling support.

While there was some caution expressed around dynamic pricing and gas coordination, participants generally preferred to retain the existing architecture, with broad agreement that any necessary refinements could be addressed after inclusion. With this decision, Glamsterdam’s CFI is now finalized, even as breakout calls continue to refine the remaining technical details.

MEV-Boost Integration Discussion

Developers revisited the long-running proposal to absorb MEV-Boost directly into consensus clients, ultimately reaffirming the existing architectural approach. Client teams broadly agreed that while direct builder connectivity will be supported, MEV-Boost functionality itself will remain external to clients, preserving the current Builder API to MEV-Boost model.

Rather than pursuing deeper integration, the focus will shift toward standardizing the Builder API and improving operator experience through more consistent client flags, such as minimum bid parameters. Further discussion on these improvements is expected to continue in upcoming ACD calls.

With Devnet-2 progressing, the CFI finalized, & higher-risk changes deferred, Glamsterdam’s trajectory now clearly emphasizes containment, safety, & execution readiness. The coming weeks will determine whether client convergence & ePBS testing can advance quickly enough to preserve the upgrade timeline without reopening settled scope decisions.

If you find any issues in this blog or notice any missing information, please feel free to reach out at yash@etherworld.co for clarifications or updates.

Related Articles

  1. Ethereum Launches $2 Million Fusaka Audit Contest to Fortify Protocol Security
  2. Ethereum Developers Announce "The Weld" Repository Merger
  3. Ethereum Developers Target September 22 for Holesky Client Releases
  4. Ethereum Developers Face Blockers in Shadowfork Testing Ahead of Fusaka
  5. A New Playbook for Ethereum: Fusaka Rethinks Testnet & Mainnet Schedules

Disclaimer: The information contained in this website is for general informational purposes only. The content provided on this website, including articles, blog posts, opinions, & analysis related to blockchain technology & cryptocurrencies, is not intended as financial or investment advice. The website & its content should not be relied upon for making financial decisions. Read full disclaimer & privacy policy.

For Press Releases, project updates & guest posts publishing with us, email contact@etherworld.co.

Subscribe to EtherWorld YouTube channel for ELI5 content.

Share if you like the content. Donate at avarch.eth.

You've something to share with the blockchain community, join us on Discord!

Follow us on Twitter, Facebook, LinkedIn & Instagram.


Share Tweet Send
0 Comments
Loading...
You've successfully subscribed to EtherWorld.co
Great! Next, complete checkout for full access to EtherWorld.co
Welcome back! You've successfully signed in
Success! Your account is fully activated, you now have access to all content.