What happened
On 2026-10-15 an entry titled to persist warm access sets across reverts was merged into the Ethereum EIPs repository by EIP-Bot. The repository commit adds an EIP describing a change in how the EVM would treat so‑called "warm access" state when an execution path is reverted.
What “warm access” persistence means (in plain terms)
The proposal concerns the internal tracking of whether certain addresses or storage locations have already been accessed during execution — often described as being marked "warm." Persisting warm access sets across reverts means that when execution is rolled back (a revert), the markers that indicate prior access would remain in place rather than being discarded.
Why this matters
- Client behaviour: The proposal targets EVM execution semantics that client implementations implement. Changes to how warm-access state is handled require client authors to review and, if they choose to adopt the EIP, change their implementations accordingly.
- Developers and gas characteristics: The way warm accesses are tracked influences gas accounting and the observed gas cost patterns of contracts. Keeping warm markers after a revert can affect the gas cost of subsequent operations in the same transaction, so smart contract authors and tooling providers should be aware of the proposal while it progresses.
Status and next steps
The change recorded in the EIPs repository is an addition of an EIP document; repository merge does not by itself change running clients or the Ethereum protocol. Any practical effect—such as client releases, testing, or eventual activation on networks—depends on follow‑up implementation and adoption steps by client teams and the wider community.
What to watch
- Client repositories and release notes for implementations that adopt the EIP.
- Discussion threads and specification updates in the EIPs repository for technical details, rationale and edge cases.
- Tooling and gas-analysis updates from developer tooling vendors and auditors.
If you maintain nodes, work on clients, or develop smart contracts, keep an eye on the EIPs repository and client release channels for concrete implementation plans and timelines.