Axelar Network: control-plane safety record
5 indexed control-plane surfaces for Axelar Network, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x4F4495243837681061C4743b74B3eEdf548D56A5, 0x7Acbae6CBa67d78AAf69e47000884aE00F9B2525, 0xB5FB4BE02232B1bBA4dC8f81dc24C26980dE9e3C, 0xCC940AE49C78F20E3F13F3cF37e996b98Ac3EC68.
What differs
Changed / discrepant
- Gateway implementation and auth module differ from the deployment config: AxelarGateway 0x4F4495243837681061C4743b74B3eEdf548D56A5: implementation() = 0x16C22cbDD77350b1AC88AdDA344F691c12f41960, authModule() = 0x3d3C73E91B1b0C243f1437F2d8363b1D5B093BD0 … observed vs axelar-contract-deployments (mainnet config, chains.ethereum, linked from docs.axelar.dev): '"implementation": "0x99B5FA03a5ea4315725c43346e55a6A6fbd94098"' / '"authModule" … documented
Show the full onchain evidence
AxelarGateway 0x4F4495243837681061C4743b74B3eEdf548D56A5: implementation() = 0x16C22cbDD77350b1AC88AdDA344F691c12f41960, authModule() = 0x3d3C73E91B1b0C243f1437F2d8363b1D5B093BD0 (whose owner() is the gateway); the deployment config lists implementation 0x99B5FA03a5ea4315725c43346e55a6A6fbd94098 and auth module 0xE3B83f79Fbf01B25659f8A814945aB82186A8AD0.
Show the full documented text
axelar-contract-deployments (mainnet config, chains.ethereum, linked from docs.axelar.dev): '"implementation": "0x99B5FA03a5ea4315725c43346e55a6A6fbd94098"' / '"authModule": "0xE3B83f79Fbf01B25659f8A814945aB82186A8AD0"'
Matched
- Gateway governed by Axelar governance (AxelarServiceGovernance): matches the documentation
- Mint limits set by a 3-of-6 multisig, as configured: matches the documentation
- Governance timelock: 3 days, plus a documented operator fast path: matches the documentation
- Interchain Token Service owned by the Axelar governance contract: matches the documentation
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Weak · 0s: an operator can execute approved proposals without waiting the timelock delayEvidence: axelar-network-governance-timelock-s25: operator() = 0xc8a8399c3D1207f4e109673be7047604737c1D56 (no contract code), which can run executeOperatorProposal immediately (no delay) for proposals Axelar …
- Signer quorum
- Not determined · No signer quorum in the published records
- Emergency / freeze scope
- Not determined · Pause / freeze authority present; its holder is not determinedEvidence: axelar-network-its-owner-s25: paused() = false.
- Docs-vs-chain parity
- Weak · Documentation differs from the chain (parameter delta)
Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.
Check it live (free)
The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x4F4495243837681061C4743b74B3eEdf548D56A5"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x4F4495243837681061C4743b74B3eEdf548D56A5"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x4F4495243837681061C4743b74B3eEdf548D56A5"})Gateway implementation and auth module differ from the deployment config
Observed onchain. AxelarGateway 0x4F4495243837681061C4743b74B3eEdf548D56A5: implementation() = 0x16C22cbDD77350b1AC88AdDA344F691c12f41960, authModule() = 0x3d3C73E91B1b0C243f1437F2d8363b1D5B093BD0 (whose owner() is the gateway); the deployment config lists implementation 0x99B5FA03a5ea4315725c43346e55a6A6fbd94098 and auth module 0xE3B83f79Fbf01B25659f8A814945aB82186A8AD0.
Documented. axelar-contract-deployments (mainnet config, chains.ethereum, linked from docs.axelar.dev): '"implementation": "0x99B5FA03a5ea4315725c43346e55a6A6fbd94098"' / '"authModule": "0xE3B83f79Fbf01B25659f8A814945aB82186A8AD0"'
cast call 0x4F4495243837681061C4743b74B3eEdf548D56A5 \ "authModule()" \ --block 26434786 --rpc-url "$ETH_RPC_URL" cast block 26434786 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xb712439847099ec3e8b1617aafd1bc7ece29e22a88dc4e7c8afcf05e6944d987
Gateway governed by Axelar governance (AxelarServiceGovernance)
Observed onchain. AxelarGateway 0x4F4495243837681061C4743b74B3eEdf548D56A5: governance() = AxelarServiceGovernance 0x7Acbae6CBa67d78AAf69e47000884aE00F9B2525 (governanceChain() = 'axelar').
Documented. docs.axelar.dev (EVM contracts owned by governance contracts) / deployment config (AxelarServiceGovernance entry): 'Axelar's contracts on other chains, such as the gateway, gas service and Interchain Token Service on EVM chains, are owned by governance contracts that only accept commands from Axelar governance.' / '"address": "0x7Acbae6CBa67d78AAf69e47000884aE00F9B2525",' / '"governanceAddress": "axelar10d07y265gmmuvt4z0w9aw880jnsr700j7v9daj",'
cast call 0x4F4495243837681061C4743b74B3eEdf548D56A5 \ "governance()" \ --block 26434786 --rpc-url "$ETH_RPC_URL" cast block 26434786 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xb712439847099ec3e8b1617aafd1bc7ece29e22a88dc4e7c8afcf05e6944d987
Mint limits set by a 3-of-6 multisig, as configured
Observed onchain. AxelarGateway 0x4F4495243837681061C4743b74B3eEdf548D56A5: mintLimiter() = Multisig 0xCC940AE49C78F20E3F13F3cF37e996b98Ac3EC68: signerThreshold() = 3 of 6 signer accounts.
Documented. axelar-contract-deployments (mainnet config): '"threshold": 3,' / '"address": "0xCC940AE49C78F20E3F13F3cF37e996b98Ac3EC68",'
cast call 0xCC940AE49C78F20E3F13F3cF37e996b98Ac3EC68 \ "signerThreshold()" \ --block 26434786 --rpc-url "$ETH_RPC_URL" cast block 26434786 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xb712439847099ec3e8b1617aafd1bc7ece29e22a88dc4e7c8afcf05e6944d987
Governance timelock: 3 days, plus a documented operator fast path
Observed onchain. AxelarServiceGovernance 0x7Acbae6CBa67d78AAf69e47000884aE00F9B2525: minimumTimeLockDelay() = 259200s (3 days); operator() = 0xc8a8399c3D1207f4e109673be7047604737c1D56 (no contract code), which can run executeOperatorProposal immediately (no delay) for proposals Axelar governance approved.
Documented. deployment config (minimumTimeDelay, operator) / docs.axelar.dev (operator approvals): '"minimumTimeDelay": 259200,' / '"operator": "0xc8a8399c3D1207f4e109673be7047604737c1D56",' / 'does the same, and can also approve proposals for an operator to execute without waiting for the timelock, so that changes can be coordinated with other network upgrades.'
cast call 0x7Acbae6CBa67d78AAf69e47000884aE00F9B2525 \ "minimumTimeLockDelay()" \ --block 26434786 --rpc-url "$ETH_RPC_URL" cast block 26434786 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xb712439847099ec3e8b1617aafd1bc7ece29e22a88dc4e7c8afcf05e6944d987
Interchain Token Service owned by the Axelar governance contract
Observed onchain. InterchainTokenService 0xB5FB4BE02232B1bBA4dC8f81dc24C26980dE9e3C: owner() = AxelarServiceGovernance 0x7Acbae6CBa67d78AAf69e47000884aE00F9B2525; paused() = false.
Documented. docs.axelar.dev (contract addresses / ITS): 'Axelar's contracts on other chains, such as the gateway, gas service and Interchain Token Service on EVM chains, are owned by governance contracts that only accept commands from Axelar governance.' / '0xB5FB4BE02232B1bBA4dC8f81dc24C26980dE9e3C'
cast call 0xB5FB4BE02232B1bBA4dC8f81dc24C26980dE9e3C \ "owner()" \ --block 26434786 --rpc-url "$ETH_RPC_URL" cast block 26434786 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xb712439847099ec3e8b1617aafd1bc7ece29e22a88dc4e7c8afcf05e6944d987
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Axelar Network differs from what the protocol documents. It turns to the emerald Aligned · Base EAS shield only when the on-chain state or the documentation changes and the two match at a new finalized block, whoever requests the re-check.
Embed this badge (it updates when the status changes):
[](https://pacta.wtf/protocols/axelar-network/)
<a href="https://pacta.wtf/protocols/axelar-network/"><img src="https://pacta.wtf/badges/axelar-network.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/axelar-network.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/axelar-network.svg.
Maintaining Axelar Network? Verify and reconcile the record
Two paths, both public. A free doc-update notice asks the maintainers to correct the documentation or the onchain parameter; anyone can send it. A Full Control-Plane Dossier ($2,500–$5,000 USDC, 24h SLA) re-reads the multisig and timelock control planes on archive RPCs and prepares an upstream docs reconciliation PR. Either way the classification changes only when the onchain state or the documentation aligns at a new finalized block.
Need procurement paperwork? Request a commercial invoice (PDF).