ACDE #246 · Sepolia 200M Signal at fork
AllCoreDevs - Execution #246 · 2026-09-24
The testnet gas limit starts rising toward 200M at the same time as the fork
Sepolia confirmed it will start signaling a 200M gas limit at the same time as the Glamsterdam fork. The call also sorted through the candidates for the next fork, Hegotá, and moved more than nine EIPs to Considered for Inclusion (CFI).
Why it matters
Glamsterdam's scaling path, which raises the gas limit from 60M to 200M, enters real-world validation on the testnet. The scope of Hegotá also took shape through the batch CFI, making the list of features that wallets, L2s, and developers need to prepare for more concrete.
Decisions
- Sepolia gas 200M: Agreed to signal a 200M gas limit at Sepolia's Glamsterdam fork. This means the limit starts rising right after the fork by the 1/1024 voting mechanism, with no staged increase.
- CL retention period: Shortening the consensus layer (CL) block retention period is not a hard fork change and does not block Gloas, so it was agreed to settle it asynchronously. This means the conclusion will come from a Discord discussion outside the call.
- EIP-8304 excluded: EIP-8304 (trustless log index) was excluded from Hegotá. This means it has finally dropped out of the candidates for this fork.
- EIP-7979 opcodes: EIP-7979 (EVM call and return opcodes) was moved to Considered for Inclusion in Hegotá. This means the clients will review it on the assumption that they will implement it.
- EIP-8163 reservation: EIP-8163 (reserving the EXTENSION 0xae opcode) was moved to Considered for Inclusion in Hegotá. It guarantees that one opcode that does nothing on L1 will not be used for any other purpose.
- Gas repricing PFI: EIP-8368 and EIP-8372 stay at PFI until mainnet Glamsterdam data has accumulated for at least 30 days after the fork. This means no decision will be made without measured data.
- Batch CFI of 7: EIP-7906, EIP-8250, EIP-8272, EIP-7668, EIP-8253, EIP-3298, EIP-8131, and the BAL byte floor EIP (bundled with EIP-8131) were moved to Considered for Inclusion in Hegotá. This means the highest-rated candidates all advanced to the next stage at once.
- TCREATE on hold: The decision on EIP-8360 (TCREATE opcode) was postponed. The problem arose because Glamsterdam removes gas refunds for throwaway contracts, so it was agreed to decide together with the discussion on deprecating self-destruct.
Discussion
200M gas limit and the JUMPDEST attack
It was discovered that the gas limit schedule was missing from the Sepolia config, so the call had to decide whether to signal 200M at the fork. Meanwhile, a JUMPDEST analysis attack on devnet 8 produced a valid block that took more than 8 seconds to execute, which set off a debate over safety.
Outcome: 200M confirmed 00:30:08
CL block and BAL retention period
EIP-8061 changed the weak subjectivity period calculation, but the CL block retention period remains unchanged, so the call discussed whether to shorten it and whether to align the Block Access List (BAL) retention period with it.
Outcome: Moved to async 00:46:53
TCREATE and the fate of throwaway contracts
Because Glamsterdam removes gas refunds, the cost of throwaway contracts that are created and deleted within a single transaction rises sharply, so the call discussed whether to include TCREATE, a new opcode to replace them, in Hegotá.
Outcome: On hold 01:15:36
SETCODEFROM and the quantum transition timeline
Whether to include SETCODEFROM (EIP-8298), which lets an EOA be moved wholesale to a code account or a quantum-resistant account, in Hegotá flared up in the chat and became an impromptu agenda item.
Outcome: Deferred to the next call 01:36:11
Glossary
- SFI: Scheduled for Inclusion, the state where inclusion in the fork is confirmed
- CFI: Considered for Inclusion, a status in which clients review the proposal on the assumption that they will implement it
- PFI: Proposed for Inclusion, a status in which inclusion has been proposed and the proposal has been accepted as a candidate
- DFI: Declined for Inclusion, the state where the EIP has been excluded from the candidates for this fork
- BAL: Block Access List, data that tells in advance which state a block touches, helping parallel execution
- Reorg: reorg, a reorganization in which an already built block is pushed out of the chain
- Frames: Frames, a new transaction execution format under discussion for Hegotá
- Self-destruct: self-destruct, an EVM instruction by which a contract destroys itself
EIPs covered
- EIP-3298 Storage clearing refund and removal of the refund cap
- EIP-7668 Remove bloom filters
- EIP-7906 Verifying transaction results with state-change opcodes
- EIP-7979 EVM call and return instructions
- EIP-8037 Increase in gas cost for state creation
- EIP-8061 Higher exit and consolidation processing limit
- EIP-8131 Unified transaction content floor price
- EIP-8163 Reserving the EXTENSION (0xae) opcode
- EIP-8250 Keyed nonces for frame transactions
- EIP-8253 Raising the nonce of nonce-0 storage accounts
- EIP-8272 Recent roots for frame transactions
- EIP-8279 Block access list byte floor
- EIP-8298 SETCODEFROM code reuse instruction
- EIP-8304 Trustless log and transaction index
- EIP-8360 TCREATE opcode
- EIP-8368 CPSB recalibration for the new gas limit
- EIP-8372 Normalized State Gas Limit
- EIP-8383 Shorter consensus layer block retention period