execution/state: simplify creation storage handling after EIP-8253
Maintainers usually reply within 1 day
@yperbasis is already working on this.
Since Nov 17, 2026.
Assessment
This issue has not been assessed yet.
Description
Follow-up to #26443, which implements EIP-8253 for Bogota devnet-2 and addresses #26280.
The pinned EIP-8253 specification restores the invariant that an account with zero nonce and empty code has empty storage. After activation on a correctly configured chain, a successful CREATE or CREATE2 therefore has no old storage to erase.
Potential follow-ups
- Separate creation bookkeeping from storage clearing.
StateWriter.CreateContractcurrently represents both. It clears a storage prefix, but is also called when EIP-8246 SELFDESTRUCT leaves a balance-only account. That latter path still needs a real reset. Give callers a clear way to request the operation they need before making creation cheaper. - Avoid redundant storage cleanup for post-Bogota creation. ApplyWrites reads the committed account and, if present, walks its storage prefix. Writer.CreateContract always clears that prefix. Investigate bypassing this work where EIP-8253 guarantees empty storage. Keep serial and parallel execution consistent, and make the decision at a boundary that already knows the fork rules where possible.
- Audit creation-specific state bookkeeping using the stronger invariant. Look for work whose only purpose is handling creation over old storage. Coordinate with #24906 on the net effect of creation followed by SELFDESTRUCT. EIP-8253 alone does not justify deleting incarnation tracking, rollback handling or creation markers used by speculative execution.
Constraints and evidence
- Preserve historical execution before activation, including the existing create-over-storage tests. RPC state overrides and custom genesis allocations can also construct states outside the canonical invariant; define their handling before applying the optimization there.
- Preserve actual storage resets for account deletion and SELFDESTRUCT, and creation at a pre-funded address. Audit all implementations and callers of the writer interface.
- Keep the new-contract zero-storage read shortcut: it avoids database reads even when the underlying storage is guaranteed empty.
- Measure account reads, prefix walks, allocations and execution time for
CREATE/CREATE2at fresh and pre-funded addresses. No performance benefit has been measured yet. Avoid spreading fork flags through generic storage interfaces unless the resulting design or measured savings justify it. - Verify fork-boundary behavior, rollback, destruction/recreation, state roots and BAL agreement across serial and parallel execution.
The transaction-trace simplification is already in place: TransactionTrace uses the first journaled slot value as the transaction prestate and explicitly relies on EIP-8253. There is no separate pre-creation storage lookup left to remove there.
Related: #15443 proposed removing the creation-time storage clear under a retroactive EIP-7610 rule. EIP-8253 instead establishes the invariant at its activation boundary, so the historical behavior must remain supported. Coordinate the overlapping work rather than implementing two independent cleanups.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.6k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 820
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from erigontech/erigon
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
flaky test
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
erigontech/erigon#26230 ·
Maintainers usually reply within 1 day
-
txnprovider/txpool: pending nonce counts past gaps in the poolPossibly taken @yperbasis claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
erigontech/erigon#26014 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
tracing: expose custom error selector and raw payload in callTracer revertReasonPossibly taken @lupin012 claimed this 9 days ago. OpenRPC
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
erigontech/erigon#25928 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
txnprovider/txpool: remove redundant blob/commitment length checkPossibly taken @yperbasis claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
erigontech/erigon#25432 ·
Maintainers usually reply within 1 day
All issues in erigontech/erigon
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day