ACDT #90 · Gas repricing 75 anchor freeze
AllCoreDevs - Testing #090 · 2026-08-03
SLOAD stays at 2100, and the anchor was lowered to 75 Mgas/s and frozen.
Froze the Glamsterdam repricing numbers. By lowering the anchor from 100 to 75 Mgas/s while keeping the SLOAD price at the current 2,100, relative prices are fixed from here on and only the block gas limit is adjusted.
Why it matters
Because SLOAD is not raised to 3,000, the backward compatibility problem that would break existing contracts such as Uniswap V2 goes away. Fixing relative prices now means the Glamsterdam fork does not need to be delayed again because of repricing, and it leaves room to raise the block limit from 200M to 300M later.
Decisions
- Repricing freeze: It was decided to keep SLOAD at the current 2,100, set account writes to 9K, and fix the anchor at 75 Mgas/s, and all EL clients approved. This means the relative prices between opcodes are settled now and only the block limit will be adjusted going forward.
- Attestation 3 seconds: In the Glamsterdam fork, the attestation deadline stays at 3 seconds, and lowering it to 2 seconds was deferred to a coordinated client release after the fork, without a hard fork. The judgment is that no hard fork is needed because clients validating at 3 seconds and 2-second clients are compatible.
- discv5 only: Decided to run devnet 8 with discv5 only, without a discv4 fallback, and set mainnet to aim for the same direction. The goal is to unify the discovery protocol on discv5.
Discussion
Gas repricing numbers freeze and anchor reduction
Introducing heavier account access test cases forced the anchor to be lowered, and in exchange SLOAD could be kept cheap, so a value to fix on had to be decided.
Outcome: Confirmed 00:34:15
Keep attestation deadline at 3 seconds
Lowering it from 3 to 2 seconds would make several attack mitigations easier, but Carlos's analysis says 2 seconds is not yet safe, so it had to be decided whether to lower it in the fork.
Outcome: Deferred 00:44:00
Devnet 8 discv5-only switch
To observe discovery behavior in isolation, the discv4 fallback has to be turned off, and this was the slot to check whether that can be enforced starting with devnet 8.
Outcome: Confirmed 00:45:24
Hot start of syncing nodes with block access lists
The topic was meant to tell clients that the verifiable state access data in Block Access Lists can be used to warm caches after snap sync.
Glossary
- SFI (Scheduled For Inclusion): Status where inclusion in the fork is confirmed
- CFI (Considered For Inclusion): Status where inclusion in the fork is under consideration
- PFI (Proposed For Inclusion): Status where the proposal has been accepted and kept as an inclusion candidate
- DFI (Declined For Inclusion): Status where the proposal has been dropped from inclusion candidates
- Repricing: Work to reprice opcode gas costs so that worst-case block execution time matches
- Anchor: The throughput per second (Mgas/s) used as the pricing baseline, lowered to 75 this time
- ePBS: A design that builds proposer-builder separation into the protocol (enshrined PBS)
- Attestation deadline: The cutoff time within a slot by which validators vote on a block