-
Notifications
You must be signed in to change notification settings - Fork 29
docs(releases): coordinator v2.1.0 migration #1002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 file reviewed, no comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm w nits
Co-authored-by: Noah B. 🥂 <[email protected]>
Co-authored-by: Noah B. 🥂 <[email protected]>
…o chore/client_manager_ts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two minor little comments from me
Description
Migrating to coordinator v2.1.0 is tedious and error prone, as the migration message must include all active provers, gateways and verifiers. This script simplifies migration by automatically constructing and submitting the migration message. This script allows migration to be performed either directly, or through a governance proposal.
Reference (Old PR): #883
Testing This Script
I manually tested this script on a custom devnet to ensure that it works. The following steps were followed:
Deploy a devnet that has the updated
Multisig
andCoordinator
contracts already deployed. The specific Amplifier commit SHA was62b966a8091d6e69fab87269811aef20007f7ead
. In this case, the coordinator v2's code id was 1.Checkout Amplifier tag coordinator-v1.1.0.
Build the coordinator v1.1.0 wasm file by running
cargo wasm
Store the resulting
coordinator.wasm
file on the devnet by runningaxelard tx wasm store coordinator.wasm --from amplifier --gas auto --gas-adjustment 2
(Code id = 21)Instantiate coordinator v1.1.0 by running
axelard tx wasm instantiate 21 '{"governance_address": "axelar1qmwn4h49quvhu49jmq22g3k0mxe0wy66ry74v5", "service_registry": "axelar1k3rj2w96va80k2uxhfn7nw7nz9xachzwaywpwdz4zygh5pqs8rys783q7y"}' --from amplifier --gas auto --gas-adjustment 2 --label 'Coordinator1.1.0' --admin axelar1qmwn4h49quvhu49jmq22g3k0mxe0wy66ry74v5
(COORD = coordinator address)This devnet had active chains 'ganache-2', 'ganache-3', 'sui' and 'stellar'. I provided coordinator v1.1.0 partial information by uploading provers only for ganache-2 and ganache-3.
-
axelard tx wasm execute $COORD '{"register_prover_contract": {"chain_name": "ganache-2", "new_prover_addr": "axelar1vf4klmh2sazym7fwn4jhn22wvtuvk5fdgakfry772y3ha3rx76zswh8vn4"}}' --from amplifier --gas auto --gas-adjustment 2
-
axelard tx wasm execute $COORD '{"register_prover_contract": {"chain_name": "ganache-3", "new_prover_addr": "axelar18sc4hkxtykcrm7a3hr6uwasw2nynv5zz33f7dlhn96xvfnyadprssm7zrq"}}' --from amplifier --gas auto --gas-adjustment 2
Verify that provers have been registered by querying all state
axelard q wasm contract-state all $COORD
. Found result:- key: chain_prover_mapganache-2, value: "axelar1vf4klmh2sazym7fwn4jhn22wvtuvk5fdgakfry772y3ha3rx76zswh8vn4"
- key: chain_prover_mapganache-3, value: "axelar18sc4hkxtykcrm7a3hr6uwasw2nynv5zz33f7dlhn96xvfnyadprssm7zrq"
Perform dry migration to check migration message:
npx ts-node cosmwasm/migrate/migrate.ts migrate 1 --address $COORD --deposit 20000000 -e devnet-solomon --dry
. Output:Migration message looked fine, as it filled in the missing sui and stellar information. The migration script is run now:
npx ts-node cosmwasm/migrate/migrate.ts migrate 1 --address $COORD --deposit 20000000 -e devnet-solomon --proposal -m $MNEMONIC
Query the devnet for the proposal information:
axelard q gov proposal 3
. Output:Greptile Summary
Updated On: 2025-09-08 21:02:17 UTC
This PR adds comprehensive release documentation for the Coordinator v2.1.0 CosmWasm contract deployment. The new release introduces significant functionality that allows the coordinator to programmatically deploy and register gateway, voting verifier, and multisig prover contracts for new chains, effectively automating the chain integration process.
The release requires a coordinated upgrade of three interconnected contracts: Coordinator (v1.1.0 → v2.1.0), Router (v1.2.0 → v1.3.0), and Multisig (v2.1.0 → v2.3.0). All three contracts require state migration, with the Router and Multisig contracts now storing the coordinator's address for proper authorization. The deployment process is structured in phases: upload new bytecode for all three contracts, then migrate each contract in sequence.
The documentation follows the established pattern used throughout the
/releases/cosmwasm
directory, providing detailed deployment instructions for all environments (devnet-amplifier, stagenet, testnet, mainnet), comprehensive verification steps, and environment-specific configuration tables. This change integrates well with the existing release documentation structure and maintains consistency with other CosmWasm contract releases in terms of format and completeness.Important Files Changed
Changed Files
releases/cosmwasm/2025-09-Coordinator-v2.1.0.md
Confidence score: 4/5
Sequence Diagram