ACDT2026-08-17_092

AllCoreDevs - Testing #092

2026-08-17 2 decisions 194 transcript lines

Transcript

At a glance

ACDT consensus: remove EIP-7610 from Glamsterdam; no behavior change since Geth and Reth already skip the affected tests
EIP-8253 (nonce bump for 28 special accounts) targeted for Hegota to permanently close the edge case
Glamsterdam devnet-8 → Gloas fork transition in ~2 days 17 hours

Detailed notes

Testing Progress

  • •Glamsterdam devnet-8 live; blog post and tweet published by EthPandaOps00:04:47
  • •devnet-7 will be sunset when devnet-8 transitions to Gloas00:05:38
  • •SSZ testing deferred to testnets; validator set smaller than prior devnet00:07:19

El Eip Discussion

  • •EIP-7610 (non-empty storage revert on contract deploy): Geth and Reth already skipping its tests; hash collision prerequisite breaks broader Ethereum security anyway00:10:46
  • •EIP-8253 proposed for Hegota: bumps nonce on the 28 special mainnet accounts, permanently closing the edge case00:13:55
  • •Consensus to remove EIP-7610 from Glamsterdam; jochem to raise at ACDE in ~1.5 weeks00:20:43

Action items

  • •Raise EIP-7610 removal from Glamsterdam at next ACDE for formal decisionjochem-brouwer
  • •Place EIP-7610 / EIP-8253 discussion reference at ACDC this weekjochem-brouwer

Agenda

From the call issue #2186Show

Devnet status updates

  • Updates on glamsterdam-devnet-8

Discussions

TBD

EL breakout

CL breakout

Key decisions

  • ACDT consensus: remove EIP-7610 from Glamsterdam; no behavior change since Geth and Reth already skip the affected tests

    DFIGeth and Reth already skip the affected tests; hash collision prerequisite breaks broader Ethereum security anyway
  • EIP-8253 (nonce bump for 28 special accounts) targeted for Hegota to permanently close the edge case

    SFIBumps nonce on the 28 special mainnet accounts to permanently close the edge case of non-empty storage on contract deploy

EIPs discussed

AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.