chore(deploy): add LayerSwapFacet v1.0.0 to hyperevm

[gvladika]

Which Linear task belongs to this PR?

Ref EXSC-220

Why did I implement it this way?

Follow-up to the LayerSwapFacet v1.0.0 production rollout (#2061), which shipped 39 networks and parked hyperevm because its deploy tx exceeded the chain's block gas limit. HyperEVM routes each address's transactions into either small blocks (~2–3M gas) or big blocks (30M gas); the facet deploy only fits a big block. With big blocks now enabled on the production deployer wallet, the facet was deployed to hyperevm via CREATE3 at 0x4Bbe85750F2625F058285bf6ff857cd90746E1ac and registered through a timelock-wrapped diamondCut Safe proposal (nonce 47, safeTxHash 0xf9af85f1b0fd7c58f14e6798593df4ed4d96e3d62a6fba72e1f8ed2c7046e190). The production hyperevm.diamond.json registry updates only once the cut executes after the timelock delay, so this PR only records the deployed address in deployments/hyperevm.json. Explorer verification is pending on indexer lag and does not affect signing or execution.

Production proposal

Chain	LayerSwapFacet address	Safe nonce
hyperevm	0x4Bbe85750F2625F058285bf6ff857cd90746E1ac	47

Checklist before requesting a review

• I have performed a self-review of my code
• This pull request is as small as possible and only tackles one problem
• I have added tests that cover the functionality / test the bug
• For new facets: I have checked all points from this list: https://www.notion.so/lifi/New-Facet-Contract-Checklist-157f0ff14ac78095a2b8f999d655622e
• I have updated any required documentation

Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)

• I have checked that any arbitrary calls to external contracts are validated and or restricted
• I have checked that any privileged calls (i.e. storage modifications) are validated and or restricted
• I have ensured that any new contracts have had AT A MINIMUM 1 preliminary audit conducted on by <company/auditor>

[coderabbitai]

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly states the main change: adding LayerSwapFacet v1.0.0 to hyperevm.
Description check	✅ Passed	The description follows the template and provides the task, rationale, deployment details, and checklist sections.

✨ 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 deploy/exsc-220-layerswap-hyperevm

---

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.}

[coderabbitai]

Caution

Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted.

Error details

putComment timed out