ACDT #88 · Devnet-7 EIPs Ready for SFI
AllCoreDevs - Testing #088 · 2026-07-20
All devnet-7 EIPs meet the SFI criteria, ratification planned for Thursday
All EIPs in Glamsterdam devnet-7 meet the SFI criteria set by EIP-7723, so it was decided to ratify formal Scheduled for Inclusion (SFI) at Thursday's ACD call. Devnet-8 focuses on re-verifying the fork transition and cleaning up repricing, and devnet-9 focuses on non-finality chaos testing.
Why it matters
Once SFI is confirmed, the list of EIPs going into Glamsterdam is effectively fixed and the path to the testnet phase opens. However, SSZ stable containers slow clients down by 10 to 20% across the board, so optimization is needed before mainnet.
Decisions
- Devnet 8 discv5: Devnet 8 will run on the execution layer (EL) with discv5 only, without discv4. This means unifying the node discovery protocol on the new version alone, with no legacy version.
- Devnet 7 EIPs to SFI: All Devnet 7 EIPs meet the SFI criteria, so they will be moved to SFI at the next ACD call on Thursday, conditional on ratification there. Inclusion in Glamsterdam effectively moves into the confirmed stage.
- EIP-7773 Review: It was decided to move EIP-7773, the Glamsterdam meta EIP, to Review, and there were no objections. The document that bundles the full specification of the upgrade enters the review stage.
- Closing the EIP-7997 PR: It was decided to close the EELS irregular state transition PR for EIP-7997. Checking whether the factory exists is unnecessary and only adds unwanted witness entries.
Discussion
SSZ stable container performance exposed by the fork transition
As the validator set grew at Devnet 7 scale, consensus layer (CL) clients hit bugs and performance degradation in SSZ stable container handling, so the call checked now whether optimization is needed before mainnet.
Proposal to unify on discv5 for Devnet 8
A proposal was made to run the node discovery protocol on the new discv5 alone, without the legacy discv4, and to use Devnet 8 as the test bed.
Promoting Devnet 7 EIPs to SFI
This was the session to check whether the EIPs in Devnet 7 meet the four SFI criteria in EIP-7723 and can formally be moved to the Scheduled for Inclusion stage.
Outcome: SFI readiness check 00:19:56
Handling the EIP-7997 contract factory in EELS
Whether to add the EIP-7997 contract factory to the EELS specification as an irregular state transition, or not to specify it since it is already deployed, was discussed because of behavioral differences between clients.
Outcome: Agreement to close the PR 00:31:31
Glossary
- SFI (Scheduled for Inclusion): Scheduled for Inclusion (SFI). The stage where an EIP is scheduled to go into the upgrade
- CFI (Considered for Inclusion): Considered for Inclusion (CFI). The stage where inclusion is being seriously examined
- PFI (Proposed for Inclusion): Proposed for Inclusion (PFI). The stage where a proposal is accepted and kept as a candidate
- DFI (Declined for Inclusion): Declined for Inclusion (DFI). The stage where a proposal has been dropped as a candidate
- ACDT / ACDE / ACDC: Core developer calls. Each covers testing, the execution layer (EL) and the consensus layer (CL) respectively
- BAL (Block Access List): Block access list, which records in advance the accounts and slots a block accesses
- SSZ stable container: A container format in Ethereum's SSZ serialization that allows fields to be extended
- Irregular state transition: A special-case process that forcibly changes state at the fork point without a normal transaction