Axelar rotates permission-control administrators for ITS, Router, and Multisig
The Ledger · · Ketju Research
Affects: Axelar (protocol)
What happened
Axelar governance passed proposal 487, executing administrator updates on three Amplifier contracts.
What changed
The permission-control administrator for the Interchain Token Service, Router, and Multisig moved from axelar1nctnr9x0qexemeld5w7w752rmqdsqqv92dw9am to axelar1kctshqfxw74usjme9mqlvkf0rgdh96ty0mmm6p.
What did not change
The record does not identify the new controller's signer set, threshold, or internal governance policy, and it reports no asset loss or route interruption.
Confirmed
- Proposal 487 passed at the June 30 voting deadline.
- The payload contains three MsgExecuteContract update_admin calls.
- All three calls set the same new administrator address.
Still open
- The identity, signer composition, threshold, and emergency powers of the new administrator remain unresolved from this record.
What it means for an advisor
- Update the Axelar control map for all three Amplifier contracts.
- Verify the new controller's composition, threshold, rotation process, and ability to migrate or pause contracts.
- Reassess whether the new controller changes the dependency's concentration or emergency-governance assumptions.
Sources
- Update permission-control admin for ITS, Router and Multisig · Axelar on-chain governance · · effective
Version 1, published . Educational research, not investment advice.