chore: update L1Migrator contract address

[rickstaa]

Updates the l1Migrator address to the new deployment 0x2a69191B43c9DB47C927bD7287F9C93838d07759.

Both contract sets in lib/chains.ts are updated:

• MAINNET_CONTRACTS (used in legacy NETWORK=MAINNET mode)
• ARBITRUM_ONE_CONTRACTS (used in production, since consumers read CHAIN_INFO[DEFAULT_CHAIN_ID].contracts.l1Migrator and the default chain is Arbitrum)

For more information see this security disclosure.

Summary by CodeRabbit

• Bug Fixes
  • Updated contract address mappings for Ethereum mainnet and Arbitrum One networks.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
explorer-arbitrum-one	Ready	Preview, Comment	Jun 2, 2026 3:13pm

[Copilot]

Pull request overview

Updates the configured l1Migrator contract address used by the explorer so migrations and related contract interactions point at the newly deployed L1Migrator (0x2a69191B43c9DB47C927bD7287F9C93838d07759). This aligns both legacy NETWORK=MAINNET behavior and the production-default Arbitrum configuration with the new deployment.

Changes:

• Updated MAINNET_CONTRACTS.l1Migrator to the new deployment address.
• Updated ARBITRUM_ONE_CONTRACTS.l1Migrator to the same new deployment address.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates the l1Migrator contract address in chain contract mappings for Ethereum mainnet and Arbitrum One networks. Both networks receive the same new address value, changing which contract address is exposed via the CHAIN_INFO configuration.

Changes

L1 Migrator Contract Address Update

Layer / File(s)	Summary
L1 Migrator address updates for mainnet and Arbitrum lib/chains.ts	The l1Migrator contract address is replaced with a new value in both MAINNET_CONTRACTS and ARBITRUM_ONE_CONTRACTS mappings.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description provides the necessary context and rationale but lacks complete alignment with the repository template structure and required sections.	Add Type of Change selection, explicit Testing section with checkboxes, Impact/Risk assessment (risk level, impacted areas, user impact, rollback plan), and link the related security disclosure issue using the template format.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the L1Migrator contract address across the codebase.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/update-l1migrator-address

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}