chore(deploy): roll out LayerSwapFacet v1.0.0 to production (39 networks)#2061
Merged
Conversation
…rks) (EXSC-220) Deploy LayerSwapFacet v1.0.0 to 38 production LiFiDiamonds via CREATE3 and a timelock-wrapped diamondCut Safe proposal per chain. Update _targetState.json to list LayerSwapFacet 1.0.0 for the deployed networks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
WalkthroughLayerSwapFacet addresses, diamond facet metadata, and version ChangesLayerSwapFacet registration
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
….0.0 Timelock diamondCut ops for LayerSwapFacet v1.0.0 executed on-chain across 39 production networks; regenerate <net>.diamond.json from on-chain state. Adds xlayer (deployed after the initial 38-network batch) to the deploy log and target state. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
gvladika
marked this pull request as ready for review
July 16, 2026 07:18
gvladika
enabled auto-merge (squash)
July 16, 2026 07:20
8 tasks
0xDEnYO
approved these changes
Jul 16, 2026
This was referenced Jul 17, 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.
Which Linear task belongs to this PR?
https://linear.app/lifi-linear/issue/EXSC-220/sc-deploy-sc-to-production (EXSC-220)
Why did I implement it this way?
Production rollout of
LayerSwapFacetv1.0.0 (audited 2026-07-15, integrated in #1711).Each production
LiFiDiamondgets the facet via CREATE3 deploy + a timelock-wrappeddiamondCutSafe proposal (one per chain). All 39 proposals have been signed, executedafter the timelock delay, and confirmed on-chain.
script/deploy/_targetState.jsonlistsLayerSwapFacet1.0.0for the deployed networks, and each<chain>.diamond.jsonfacetregistry has been regenerated from on-chain state now that the cuts executed.
Production proposals (39 networks)
0x7Babf9c78e5c040B1bBd8981189ea4d6E3Fc83440xBdD660fa7e8D31f0199E333B85a46aa43Bb3D69C0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x3aAE6eb0a3C23406F28FC63541Fd44A57839479D0x04E051D8e3627A79785f8E210B1d61A877AA737A0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0xE2F2a8e1B4F8A5f5686421BbBB90Fd8cB45ef9d90x828Cc8Dc04e22B63DFB7764cFb58Ddbc4C2A07c70x0Bb301cc98299d57Ab7d07381fF0C9E48177Fd500x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0x04E051D8e3627A79785f8E210B1d61A877AA737A0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0x455B71D20a8b51E9757FeD649833f71355cFCe440x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0x04E051D8e3627A79785f8E210B1d61A877AA737A0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737A0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0x04E051D8e3627A79785f8E210B1d61A877AA737A0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0x0Bb301cc98299d57Ab7d07381fF0C9E48177Fd500xBdD660fa7e8D31f0199E333B85a46aa43Bb3D69C0x2BfD9Ce2fe03cFf9c25d524bdAAd8E16161087Cd0x04E051D8e3627A79785f8E210B1d61A877AA737A0x04E051D8e3627A79785f8E210B1d61A877AA737Axlayerwas deployed and proposed after the initial 38-network batch (explorer verificationoriginally blocked on an OKLink key) and is included here; its cut executed on-chain in tx
0x3a9f1675e0405fa78af8db2f75ce1737bbd72c1837aa7c118af009ea746ba3a1.Not in this PR (follow-up)
abstract,sophon,zksync: needDeployLayerSwapFacet.zksync.s.sol(+ zksolc build) before deploy.ETH_NODE_URI_SWELLCHAIN.Checklist before requesting a review
Checklist for reviewer (DO NOT DEPLOY and contracts BEFORE CHECKING THIS!!!)