ACDE #243 · Glamsterdam 200M Gas Limit Confirmed

AllCoreDevs - Execution #243 · 2026-08-13

It means raising the gas limit to 200M, more than 3 times higher, is safe

The gas repricing figures (EIP-2780, 8037, 8038) were finalized, and it was concluded that a 200M gas limit is safe in Glamsterdam. 12 candidate EIPs for the next fork, Hegota, were accepted, and the decision on how to implement native AA was postponed to the August 25 breakout.

Why it matters

This opens the way for per-block processing capacity to grow to more than 3 times today's level, which directly affects fees and throughput. Whether native AA goes with Frames (EIP-8141) or EIP-8130 determines which account standard wallets and L2s will have to follow.

Decisions

Gas repricing finalized: The gas repricing figures are finalized, no spec changes are needed, and the 200M gas limit for Glamsterdam is confirmed. This means clients do not have to change their code.
EIP-8261 schedule: The in-client gas limit schedule from EIP-8261 will proceed as an optional parameter in the CL config. A schedule for raising the gas limit in stages after the fork can be built in ahead of time.
EIP-7923 memory: EIP-7923 linear memory pricing was accepted as a Hegota candidate. It proposes changing memory pricing from quadratic to linear.
EIP-3298 refunds: EIP-3298 removal of refunds was accepted as a Hegota candidate. It proposes simplifying the EVM by eliminating the gas refund given when storage is cleared.
EIP-5920 PAY: EIP-5920 PAY opcode was accepted as a Hegota candidate. It proposes creating an instruction that sends only ETH without executing the recipient's code.
EIP-8358 metering: EIP-8358 net gas metering for account changes was accepted as a Hegota candidate. It proposes discounting gas when an account that has already been modified in a transaction is modified again.
EIP-8374 Warm Set: EIP-8374 keeping warm access after revert was accepted as a Hegota candidate. It proposes not clearing the warm state of the access list even when a call fails.
EIP-8368 CPSB: EIP-8368 CPSB recalibration was accepted as a Hegota candidate. It proposes that raising the gas limit further requires re-tuning the constants of EIP-8037.
EIP-8077 nonce: EIP-8077 transaction announcements with nonce was accepted as a Hegota candidate. It proposes attaching the sender and nonce to transaction hash announcements so the mempool can select more intelligently.
EIP-8094 mempool: EIP-8094 blob-aware mempool was accepted as a Hegota candidate. It proposes preventing mempool traffic from concentrating when blob fees spike.
EIP-8355 ML-DSA: EIP-8355 ML-DSA precompile was accepted as a Hegota candidate. It proposes using a standard library for FIPS 204 quantum-resistant signature verification instead of having clients implement it themselves.
EIP-8372 state gas: EIP-8372 normalized state gas limit was accepted as a Hegota candidate. It proposes recalibrating the price once at fork time to match post-Glamsterdam state creation demand.
EIP-8375 eMBER: EIP-8375 eMBER was accepted as a Hegota candidate. It proposes burning part of the execution reward to reduce the impact of large execution rewards on security.
EIP-8219 arithmetic: EIP-8219 checked arithmetic opcodes were accepted as a Hegota candidate. It proposes adding safe arithmetic instructions that automatically revert on overflow.
5 EIPs excluded: EIPs 7971, 8058, 7609, 7973 and 8360 were not accepted as candidates. Their champions (the people responsible for pushing a proposal forward) were not on the call, so nixo will contact the proposers and close the PRs if they cannot be reached.
AA decision deferred: The decision on native AA implementation (Frames 8141 vs 8130) was postponed to the August 25 AA breakout and the August 27 ACDE. Which account abstraction approach to use has not yet been decided.
Preference list deadline: EL clients agreed to submit their preference lists for Hegota candidates by September 10 (ACDE #245). These lists will be used to narrow down what gets included.

Discussion

EIP-8261: Putting the gas limit into the CL config as a schedule

A proposal to write the post-fork gas limit increase schedule into the CL config file in advance, to prevent the risk of the gas limit rising before repricing is complete, was put to a vote.

Outcome: Confirmed decision 00:20:18

History expiry: how much to delete

With state growing by 120GB a year at a 200M gas limit, history expiry, which deletes old block data, is needed to protect 2TB node operators, but the problem was raised that each client has a different default.

EIP-8374: Keep Warm Access After Revert

On the proposal to keep access list entries warm even when a call fails, an experience-based warning was raised that the implementation may be larger than it looks.

Outcome: PFI decision 00:42:17

Frames vs. EIP-8130: How to Implement Native AA

At ACDE 233 in March, the group agreed to include native AA (account abstraction) in Hegotá but did not settle the concrete implementation. On this call, client support for frames (EIP-8141) collided head-on with pushback from L2s.

Outcome: Postponement decision 01:34:59

Glossary

PFI: Proposed for Inclusion: proposed and accepted as a candidate for inclusion in the fork
CFI: Considered for Inclusion: under review for inclusion in the fork
SFI: Scheduled for Inclusion, the state where inclusion in the fork is confirmed
DFI: Declined for Inclusion, the state of being removed from inclusion candidacy
Champion: The person who takes responsibility for an EIP, explains it, and pushes it forward
Native AA: Building account abstraction, which makes wallet accounts programmable, directly into the protocol
Frames: A native AA proposal (EIP-8141) that splits transaction validation and execution into frames so that an account can define its own validation method
History expiry: Nodes delete old block data to reduce the storage burden

EIPs covered

Forkcast record · Recording · ← Core Dev Calls