Meeting Summary:
The team reviewed updates on various testnets and discussed bug fixes, with particular attention to the Prism client issue that will require a delayed release. They examined several Ethereum Improvement Proposals (EIPs) related to validator consolidation, staking incentives, and network optimization improvements, with ongoing discussions about their implementation and potential impacts. The conversation ended with discussions about the Glamsterdam upgrade, including the inclusion of Fossil and the naming of the H-star upgrade, while emphasizing the importance of balancing scaling efforts with other EIPs.
Click to expand detailed summary
The team reviewed updates on the Sepolia and Hoodi forks, noting that Sepolia BP02 went smoothly with no issues, while Hoodi saw a small drop in participation due to operator issues and a Reth bug that has since been patched. They discussed the specific combination of conditions that triggered the bug and agreed to explore adding a static test for it. The team confirmed the mainnet release date for Fusaka as November 3rd, with the Fork scheduled for December 3rd and BPO1 on December 9th, with BPO2 set for January 7th of the following year.
The team discussed a bug in the Prism client that was not present in testnets, causing non-prism peers to be kicked out after a few hours. They decided to proceed with the mainnet dates but delay the Prism release, with Manu noting that a fix might not be ready by Monday. The team agreed to keep an eye on the issue and adjust if necessary. They also discussed setting up a point person per team for incident responses and reviewed a process document for the Fusaka hard fork.
The team discussed the timing and process for reviewing EIPs related to the CL layer, with a focus on having client teams submit written proposals by November 13th for review at the next ACDC meeting. They reviewed EIP-7688, which introduces stable containers, and EIP-8045, which modifies proposer shuffling to exclude slash validators, with Barnabas noting that the proposer lookahead feature would make this relatively straightforward to implement. The team agreed to continue scoping discussions over the next two weeks, with client teams preparing proposals for the CL side of the fork.
The meeting discussed two Ethereum Improvement Proposals (EIPs): 8045 and 8061. EIP 8045 is a simple one-line change to prevent issues with ExLC/validators, while EIP 8061 proposes increasing churn limits for entries, exits, and consolidations, which would improve staking UX but reduce the time for weak subjectivity to around 6 days. Ansgar raised concerns about the implications of EIP 8061 on issuance changes, suggesting it could lead to faster, unanticipated changes in staking dynamics. The group agreed to further consider the proposal’s implications and potential modifications to address these concerns.
The team discussed two EIPs related to validator consolidation and staking incentives. Anders presented EIP-8062, which adds a small fee to SWAP withdrawals to incentivize moving from skimming to compounding validators, and EIP-8068, which adjusts the effective balance calculation to make compounding validators more favorable. The group debated whether these changes would actually encourage consolidation, with some members suggesting that larger staking providers might not be held back by these incentives. Mikhail raised concerns about the low adoption of compounding validators and questioned whether the proposed changes would have a meaningful impact on adoption rates.
The team discussed two main topics: a proposed fix for validator consolidation issues (EIP-8062) and network optimization improvements. Mikhail explained that the consolidation fix is a “nice-to-have” UX improvement rather than a security issue, while Raúl presented Peer DAS CL-level deltas, a network optimization that would allow increasing the maximum number of blobs from 21 to 72, with implementation expected by February. The team agreed to align this optimization work with the Glamsterdam release, with Raúl proposing a timeline that would see full interoperability by November and production-grade implementations by December, allowing for formal testnet journeys leading to mainnet.
The meeting focused on scaling efforts for Ethereum, particularly the Glamsterdam initiative. Participants discussed the importance of scaling and the need to balance it with other EIPs. There was a question about whether client teams felt comfortable with three more BPOs while finishing Glamsterdam, to which Stokes responded that it could be manageable if non-consensus changes on the networking layer are considered. The group also discussed the partial message extension and its potential merge into libp2p. The conversation ended with a brief mention of EIP7805, which was CFI’d but could be reconsidered for the fork scope.
The meeting focused on the inclusion of Fossil in the Glamsterdam upgrade, with participants discussing the trade-offs between shipping cadence and potential risks to censorship resistance. Soispoke outlined the considerations around Fossil’s importance and timing, while Ansgar highlighted the challenge of balancing timeline impacts with the need for Fossil. The group agreed to move forward with HECA as the name for the H-star upgrade, and participants were encouraged to refine their forkcast data for better presentation.
Next Steps:
- Prism team : Release mainnet-ready version as soon as possible
- stokes: Reach out to all teams to get a point person per team for incident response and add to Fusaka process doc PR
- Reth team: Continue work on patched testlist for the bug found on Hoodi
- Testing team : Create explicit static test for the Reth bug scenario
- All client teams: Submit written proposals for Glamsterdam CL scoping by next ACDC
- EL implementers: Prepare to rehash and merge GetBlobsB3 Engine API PRs by November for PeerDAS cell-level deltas
- CL implementers : Review and comment on PeerDAS specs, start planning implementation by November
- CL implementers : Begin implementation of PeerDAS by December
- Lighthouse team: Continue PeerDAS implementation and conduct interop tests with Prism prototype
- Raul: Share PeerDAS presentation materials publicly after the call
- stokes: Work with Raul to get PeerDAS information posted somewhere public for reference
- stokes: Consider better language for the process doc regarding testnet requirements before setting mainnet dates
- All teams: Review EIP-7688 and specs PR 4630
- All teams: Review EIP-8045
- All teams: Review EIP-8061 considering weak subjectivity implications
- All teams: Review EIP-7805 for potential Glamsterdam inclusion
- Community: Submit proposals for Fusaka mascot if desired
Recording Access:
Holešky Oct 1,