chore: record Universal Router 2.1.2 deployment addresses - #167
Merged
Merged
Conversation
Adds the UniversalRouter#v2.1.2 entry to the deployment records for the 23 chains that have a deployments file in this repo. 2.1.2 was deployed from the universal-router repo rather than through the briefcase, so there are no broadcast logs or task files to accompany it — addresses, deployment transactions and initcode hashes are taken from that repo's broadcast output and cross-checked against the 2.1.2 release notes. Base Sepolia (84532) and HyperEVM (999) are omitted: neither has a deployments file here today. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ericneil-sanc
approved these changes
Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the
UniversalRouter#v2.1.2deployment across the 23 chains that have a deployments file in this repo. The dev portal reads these files, so 2.1.2 is currently missing from it — see this thread.Purely additive: 46 files, 690 insertions, 0 deletions. Each chain gets a TOC line, a summary-table row, a detail section and a
latestJSON entry, matching the existing forge-chronicles shape.Why there are no broadcast files
2.1.2 was deployed from the
universal-routerrepo rather than through the briefcase here, so there is no broadcast log, task file or submodule bump to accompany it. Addresses, deployment transactions and initcode hashes come from that repo's broadcast output; the initcode hashes were re-derived askeccak(tx.input)and confirmed against the entry already recorded for mainnet.Verification
Every recorded address was checked per-chain against both the 2.1.2 release notes and
universal-router/deploy-addresses/— 23/23 agree on all three. The.mdsummary row,.mddetail section and.jsonentry were also checked against each other: 23 chains, 0 mismatches.HyperEVM is worth a separate look: its 2.1.2 is live and verified (bytecode identical to Base's 2.1.2 apart from immutables), but it has no entry in
universal-router/deploy-addresses/and no broadcast log, so it reached the release notes through a path neither repo records.Overlap with #165
#165 also adds 2.1.2 for mainnet, sepolia and ink (6 files). The values here are pinned to be byte-identical to that PR, so the content agrees — but whichever merges second will need a rebase. Mainnet is included here deliberately, since
deployments/1.mdis the file the dev portal is serving stale.Notes: commit-hash links point at
universal-router(where802fe4cactually lives) rather than thegit@github.com:Uniswap/contracts/...form used by older entries. Timestamps for the 20 chains not shared with #165 come from broadcast run time, so they are within ~30s of block time.🤖 Generated with Claude Code