Agenda
Fusaka:
- Mainnet BPO outcome
Glamsterdam:
- bal-devnet-0/1 updates and scope discussion
- epbs-devnet-0 update
EIP-8037 decision for glamsterdam
Meeting Time: Monday, January 19, 2026 at 14:00 UTC (60 minutes)
Fusaka:
- Mainnet BPO outcome
Glamsterdam:
- bal-devnet-0/1 updates and scope discussion
- epbs-devnet-0 update
EIP-8037 decision for glamsterdam
Meeting Time: Monday, January 19, 2026 at 14:00 UTC (60 minutes)
The team reviewed and discussed various Ethereum Improvement Proposals (EIPs) for inclusion in DevNet 2, including updates on block-level access, transaction receipts, and state growth strategies. They made decisions about specific EIP implementations and agreed to update the specs page with relevant caveats while aiming for a local devnet version with simplified scope. The conversation ended with discussions about dynamic pricing impacts and MEV-Boost functionality, with plans to continue further conversations asynchronously.
The team discussed updates on block-level access with devnets, focusing on syncing fixes and stable performance with EVM fuzzing and Uniswap trades. They decided to keep EIP 7843, an Engine API change, in DevNet 2 since Lodestar has already merged the PR, and Barnabas confirmed that Lighthouse updates would be ready soon. The team also agreed to deny the inclusion of EIP 8024, a switch encoding change, in DevNet 2 for now, and to revisit it on ACD if necessary. Finally, Tony presented EIP 7778 for alignment on specs, but the transcript ends before further discussion.
The team discussed changes to transaction receipts, focusing on gas usage accounting and EIP-7778 implementation. Toni proposed adding a new field to receipts to track gas spent post-refund, which received general agreement from Ben and Daniel, though Parithosh suggested moving it to DevNet 2 for broader testing. The team also reviewed EIP-7708, deciding to keep the system address and merge the PR as-is, with Spencer confirming the address choice was reasonable for now. Stefan indicated DevNet 2 would likely launch around Wednesday, pending PR merges and client readiness, with Potuz noting Prysm’s develop branch was actively merging PRs for the spec.
The team discussed the status of various Ethereum clients for devnet testing, with Prysm and Teku appearing to be the most advanced. They agreed to aim for a local devnet version with simplified scope, excluding external builders and P2P broadcast of bids, while EIPs 7843, 7778, 7708, and 8024 were confirmed for inclusion in devnet-2. The team decided to update the specs page with these caveats and to aim for a local devnet version to begin testing, with a timeline of a few weeks rather than the initially suggested 11 days.
The meeting focused on discussing EIP 8037, which proposes a strategy for state growth in Glamsterdam. The group decided to CFI (Consensus Fallback Implementation) the EIP as-is, with plans to iterate on it asynchronously. They also discussed the potential impact of dynamic pricing on smart contracts and agreed to gather more feedback from the developer community. Additionally, there was a brief discussion about absorbing MEV-Boost functionality into clients for Glamsterdam, with some uncertainty about the scope of specification needed. The conversation ended with plans to continue discussions asynchronously in various channels.
4cKs?Mwh)4cKs?Mwh)4cKs?Mwh)YouTube Stream Links: