Skip to content

fix: update the L1 AnchorStateRegistry and DelayedWETH addresses - #703

Open
erkancamli wants to merge 1 commit into
inkonchain:mainfrom
erkancamli:fix/l1-dispute-addresses
Open

erkancamli wants to merge 1 commit into
inkonchain:mainfrom
erkancamli:fix/l1-dispute-addresses

Conversation

@erkancamli

Copy link
Copy Markdown

The L1 contract tables on the Contracts page still list the AnchorStateRegistry and DelayedWETHPermissionedGame proxies from the original deployment. The superchain-registry (superchain/extra/addresses/addresses.json, chain ids 57073 and 763373) lists different addresses for Ink Mainnet and Ink Sepolia:

Network Contract Docs today Registry
Mainnet AnchorStateRegistryProxy 0xde74…2509 0xEe018bAf058227872540AC60eFbd38b023d9dAe2
Mainnet DelayedWETHProxy 0x1477…0d38 0x57b4C29DAee99a28E6E86778b499361294c134eA
Sepolia AnchorStateRegistryProxy 0x8912…ea1a 0x299D7Ea9f0B584cfaF2a5341D151B44967594cA9
Sepolia DelayedWETHProxy 0x180a…c456 0x8BA4e89842C56eb8a45BFB37d186f4504E55F572

The old addresses no longer appear in the registry. I checked the other L1 entries in both tables against the same file and they match (the ERC-5564/6538 singletons are not in the registry and are unchanged). The DelayedWETH row is renamed to match the registry name.

The L1 contract tables still list the AnchorStateRegistry and
DelayedWETHPermissionedGame proxies from the original deployment. The
superchain-registry (superchain/extra/addresses/addresses.json, chain
ids 57073 and 763373) now lists different AnchorStateRegistryProxy and
DelayedWETHProxy addresses for Ink Mainnet and Ink Sepolia, and the old
addresses no longer appear there. The other L1 addresses in both tables
match the registry.
@erkancamli
erkancamli requested a review from a team as a code owner October 8, 2026 15:53
@erkancamli

Copy link
Copy Markdown
Author

Friendly ping: contracts.mdx on current main still lists the addresses this PR replaces, and the change still applies cleanly. Happy to update anything else on that page if useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant