Skip to content

kip-290: clarify ABv2 proxy install runs at FORK_BLOCK - 1 finalize#120

Merged
hyunsooda merged 1 commit into
mainfrom
clarify-abv2-install-timing
May 28, 2026
Merged

kip-290: clarify ABv2 proxy install runs at FORK_BLOCK - 1 finalize#120
hyunsooda merged 1 commit into
mainfrom
clarify-abv2-install-timing

Conversation

@hyunsooda
Copy link
Copy Markdown
Contributor

@hyunsooda hyunsooda commented May 27, 2026

ABv2 proxy is installed at FORK_BLOCK - 1 finalize, not at FORK_BLOCK.

"Starting from FORK_BLOCK" is observably correct for transactions executing
at block FORK_BLOCK onward, but leaves the install timing ambiguous from the
core-client / RPC-state perspective. `eth_getCode(0x400, FORK_BLOCK - 1)`
already returns the proxy bytecode because the install hook runs at the
finalize state of block FORK_BLOCK - 1 — that 1-block precision matters for
operators (pre-deployment deadline is FORK_BLOCK - 1 finalize, not
FORK_BLOCK) and for implementers (exact hook location).

Add one normative sentence tightening this to MUST language. No semantic
change for typical readers.
@hyunsooda hyunsooda merged commit f755e69 into main May 28, 2026
5 of 6 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators May 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants