ACDT #92 · EIP-7610 Excluded from Glamsterdam
AllCoreDevs - Testing #092 · 2026-08-17
Remove a rule that guarded against an attack that cannot happen in reality
Participants agreed to drop EIP-7610 from the Glamsterdam fork. Geth and Reth already skip the related tests, so actual behavior does not change at all. Instead, EIP-8253, which removes the root of the problem, was moved up as a target for the next fork, Hegota.
Why it matters
Client teams will be able to pass the standard test suite without skipping tests, which ends the confusion that auditors and researchers have repeatedly raised. For users, this is a spec cleanup that changes no behavior.
Decisions
- EIP-7610 excluded: ACDT agreed to remove EIP-7610 from Glamsterdam. Geth and Reth already skip the relevant tests, so there is no change in behavior.
- EIP-8253 Hegota: EIP-8253, which raises the nonce of 28 special accounts, was set as a Hegota target. It permanently eliminates the exceptional situation that caused the problem.
Discussion
EIP-7610 excluded from Glamsterdam
EIP-7610, which makes a check that an account's storage is empty before contract deployment, was in Scheduled for Inclusion (SFI) status, but as people pointed out that the attack it aims to prevent is impossible without a hash collision, whether to drop it was discussed.
Outcome: Agreement to drop 00:20:43
Handling EIP-8253 in Hegota and the testing problem
The discussion covered which fork should include EIP-8253, which eliminates the 28 problem accounts themselves instead of keeping EIP-7610, and whether the same problem would recur in testing.
Outcome: Hegota target 00:13:55
Glossary
- SFI: Scheduled for Inclusion. The status where inclusion in the fork is confirmed
- CFI: Considered for Inclusion. The state of being under review for fork inclusion
- PFI: Proposed for Inclusion. The state of being proposed for fork inclusion and accepted as a candidate
- DFI: The state of being removed from fork candidacy
- ACDT·ACDE·ACDC: Ethereum core developer calls covering testing, the execution layer, and the consensus layer, respectively
- Hash collision: When two different inputs produce the same hash value. The security of Ethereum addresses rests on the assumption that this is impossible
- Nonce: An account's transaction counter. A contract cannot be deployed to an address with a nonzero value
- devnet: A temporary development network for trying out a new fork in advance