feat(multx): gate paused v0.5 testnet redeployments - #75
Merged
Conversation
Test Results
Coverage
Generated by |
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.
Outcome
Adds a fail-closed, manifest-driven procedure for deploying new paused MultX v0.5 bridge contracts to Kamet and Makalu. This does not execute a deployment and does not alter historical contracts.
Safety gates
The example includes LAX only and leaves every authority/cap/approval as a failing placeholder. Other assets require separate route/cap approval.
Validation
6bfdb3d2c8e7ae5f26169ac8c1b982c86eded4dda74a1940cbb3e88093b11cfc.npm audit --omit=devreports zero production findings. The full deployment/test toolchain audit reports 63 transitive development findings (3 critical, 14 high); keep execution isolated and complete dependency modernization before treating this toolchain as a long-lived production runner.External gate
Execution remains blocked on seven client-controlled public signer addresses/operators, governance roles, exact UTC window, rollback/responders, caps, approval record, dependency-toolchain disposition, and explicit activation authority. MultX remains disabled on LITHO mainnet.