ACDT #103 · 8037 decision postponed to Thursday
AllCoreDevs - Testing #103 · 2026-11-16
The 3.3x gas expansion proposal broke contracts, delaying the launch decision
It emerged late that EIP-8037/8038, the scaling EIPs included in Glamsterdam, break the invariants of numerous smart contracts. The final decision on whether to proceed with launch was not made on this call and was pushed to Thursday's ACDE call.
Why it matters
This change, which raises the block gas limit 3.3x from 60M to 200M, could break 10,000 to 15,000 contracts that rely on hardcoded gas values, as well as try/catch-based composability. Shipping it as is risks locking funds in some immutable protocols that cannot be redeployed, while delaying it pushes back the next fork, Hegotá, including the post-quantum account transition, by months.
Decisions
- EIP-8037 launch put on hold: No decision was made on EIP-8037 today, and the official direction will be decided on Thursday's ACDE call. This means whether to ship it as is or change it remains undecided.
- Glamsterdam delay: It was concluded that delaying the Glamsterdam schedule to give the application layer time to respond before mainnet deployment was the right call. In other words, the delay was made with apps in mind first.
Discussion
Try/catch composability breakdown
Because of EIP-8037, users can adjust gas to deliberately trigger catch blocks, undermining the trust basis of extensible protocols like Juicebox.
Invariant documentation and future guarantee scope
A shared recognition emerged that even among core developers, it is unclear which protocol properties are guaranteed forever and which can change.
Glamsterdam direction and the ACDE decision
It was reconfirmed that the final decision on whether to ship EIP-8037 as is or change it will be made not on this call but on Thursday's ACDE call.
Outcome: Decision deferred 01:30:30
Scope of audit disclosure
Discussion, mostly in chat, revolved around whether to publish the list of vulnerable contracts found by ChainSecurity and DeDaub as a public report or deliver it privately only to affected protocols.
Glossary
- SFI: Scheduled for Inclusion: the status in which inclusion in the fork is confirmed
- CFI: Considered for Inclusion, a status under review for inclusion
- PFI: Proposed for Inclusion, a status proposed and submitted as an inclusion candidate
- DFI: Status where the proposal has been dropped from inclusion candidates
- ACDT/ACDE: The Testing (T) / Execution layer (E) track distinction on AllCoreDevs calls
- Gas reservoir / refill mechanism: The gas reservation and recharge method introduced by EIP-8037
- Hegotá: The hard fork after Glamsterdam, which includes the post-quantum (PQ) account transition
- Invariant: A property the protocol guarantees is always true, a premise that contracts rely on