Axelar approves Amplifier contract-admin rotation to a multisig

What happened

Axelar governance passed proposal 492 to rotate the administrator and upgrade authority for 35 mainnet Amplifier CosmWasm contracts to a specified multisig.

What changed

Governance authorized a new upgrade-control endpoint across gateway, routing, voting, rewards, service-registry, multisig, and Interchain Token Service components.

What did not change

The governance record does not independently prove that every contract-admin update executed or disclose the destination multisig's signer identities, threshold, or internal controls.

Confirmed

• Proposal 492 passed.
• The destination address is axelar14vps3ev03zyp2wmj89etx8rrxdxyltfy4rzl5m.
• The proposal identifies 35 affected contracts.
• Affected contract families include gateways, routers, voting verifiers, multisig components, rewards, service registry, and Interchain Token Service.

Still open

• Execution and post-change admin state for each contract are not established.
• The destination multisig's signer identities, threshold, key custody, and transaction policy are not supplied.
• It is not established whether every affected contract shares identical upgrade and emergency powers.

What it means for an advisor

• Review the Axelar memo's upgrade-authority map and replace prior administrator assumptions only after contract-level verification.
• Obtain the multisig owner set and threshold before assessing whether the rotation reduces or concentrates control risk.
• Reconcile all 35 contracts because partial execution would leave mixed administrator states.