Axelar approves ITS and Amplifier gateway ownership migration

What happened

Axelar governance passed proposal 491 to schedule AxelarServiceGovernance ownership acceptance for Interchain Token Service contracts across 21 EVM chains and Amplifier gateways on Hedera, Hyperliquid, Monad, and XRPL EVM.

What changed

Governance authorized a broad cross-chain migration of ownership and administrative control to AxelarServiceGovernance.

What did not change

The record does not prove that each timelock expired, each acceptOwnership call completed, or every target's final owner state changed on July 3.

Confirmed

• Proposal 491 passed.
• The payload targets Interchain Token Service on 21 EVM chains.
• It also targets AxelarAmplifierGateway on Hedera, Hyperliquid, Monad, and XRPL EVM.
• The mechanism uses scheduled timelock proposals delivered through AxelarnetGateway calls.

Still open

• The effective ownership-acceptance transaction and final owner state for each target are not supplied.
• Per-chain timelock delays, failed calls, retries, and partial completion remain unverified.
• The full authority and internal controls of AxelarServiceGovernance require reconciliation.

What it means for an advisor

• Review the Axelar memo's cross-chain ownership and upgrade-authority map.
• Verify the owner and pending-owner state for every relevant ITS and Amplifier gateway before treating the migration as complete.
• Monitor timelock and governance dependencies separately for client-used chains.