Axelar General Message Passing (GMP) is the cross-chain primitive that lets any contract on one of Axelar's connected chains call any function on a contract on any other connected chain, with the call payload, gas, and authentication handled by Axelar's validator network. As of April 2026 GMP routes contract calls across more than 70 chains, including Ethereum, every major rollup, Solana, Sui, Aptos, Stellar, and the entire Cosmos ecosystem via IBC.
​

The architectural distinction is that Axelar is itself a Tendermint-based proof-of-stake blockchain. Validators are not just message signers — they run consensus on the Axelar chain, run light clients or full nodes for every connected chain, and stake AXL to participate. This is the same trust model as a layer-1 blockchain, applied to cross-chain messaging. The full Axelar documentation covers the model in depth, with the validator economics described in the AXL tokenomics post.
​

General Message Passing is Axelar's primitive for cross-chain function calls. A contract on Source Chain A invokes callContract on the local Axelar Gateway, specifying the destination chain, destination contract address, and payload. Axelar validators observe the event, reach consensus on its validity within the Axelar chain, and an Axelar Relayer submits a transaction on the destination chain that calls the destination contract with the verified payload.
​

The pattern subsumes asset transfers. A token transfer is just a GMP call with a payload that says "mint X tokens to address Y." Axelar's Interchain Token Service (ITS) is built on top of GMP — the service is a set of token contracts that use GMP as their messaging transport. Squid Router, the swap layer that aggregates DEXes across chains, also runs on top of GMP.
​

What separates Axelar from validator-set-based protocols like Wormhole is that Axelar's validators run consensus. They produce blocks, vote on cross-chain message validity through the same consensus mechanism that secures the chain itself, and slash misbehaving validators through the protocol's own staking system. Wormhole's Guardians do not run a chain; they sign messages but do not produce blocks or have on-chain slashing.
​

A GMP call moves through five components.
​

The application contract on the source chain calls callContract on the local Axelar Gateway. The Gateway is a smart contract deployed on every connected chain that emits a ContractCall event capturing the destination chain, destination address, and payload hash. Validators run external chain agents (called vald) that observe the event and report it to the Axelar chain. The Axelar chain reaches consensus that the event happened by running a vote where the threshold is approximately 67% of voting power. Once the vote passes, validators sign a multisig attestation. A Relayer fetches the attestation and submits an execute transaction on the destination chain's Gateway, which verifies the signatures and calls the destination contract with the payload.
​

The destination contract receives the call through the _execute entry point of the Axelar Executable interface. The interface gives the contract the source chain name, source address, and payload. Application code parses the payload and runs whatever logic the message instructs.
​

Gas payment is handled by the Axelar Gas Service. The user paying for the source-chain transaction also pays for the destination-chain execution upfront, in any token Axelar accepts as gas. Axelar Relayers convert that prepayment into the destination chain's native gas token and use it to fund the execute transaction. This means an Ethereum sender can pay Solana gas in ETH without holding SOL — a property that significantly reduces UX friction for cross-chain applications.
​

As of April 2026 the Axelar network has roughly 70 active validators and a long tail of inactive ones, per the Mintscan Axelar validator dashboard. Validators run nodes for the Axelar chain itself plus external nodes for every chain the validator chooses to support — and not every validator supports every chain.
​

Two design choices shape the security model.
​

Axelar uses quadratic voting for confirming cross-chain events. A validator's vote weight is the square root of its stake, not its raw stake. This dampens the influence of any single large validator and incentivizes broader participation in event verification. The mechanism is described in Axelar's security documentation.
​

Anyone can run a validator by acquiring AXL stake and registering. The network does not gate validator entry, though minimum stake requirements and slashing risks set practical floors. Each validator chooses which connected chains to support, and the protocol reads each validator's chain-support set when computing voting power for a specific event.
​

The trade-off is that validators with more chain-support coverage have effectively more weight in the network, since they participate in more events. A small validator that only supports two chains contributes to fewer messages than a large validator that supports forty.
​

The Interchain Token Service (ITS) is Axelar's reference token-deployment standard, comparable to LayerZero's OFT or Wormhole's NTT. ITS lets a token issuer deploy a Custom Token across any combination of Axelar-connected chains with consistent supply accounting and unified registry.
​

Three deployment modes are supported.

ITS has been adopted by stablecoin issuers, RWA platforms, and gaming projects. The full integration guide is in Axelar's Interchain Token Service documentation.
​

Squid Router is the consumer-facing swap product built on Axelar GMP. A user picks a source token on one chain and a destination token on another. Squid finds a swap path through DEXes (Uniswap, Curve, Sushi, Trader Joe, Quickswap) on the source chain, uses GMP to bridge the proceeds to the destination, then runs another DEX swap on the destination side to deliver the target token.
​

The pattern is a single user transaction that internally chains: source-chain swap → GMP message → destination-chain swap. Squid is one of the most-used GMP applications and has been integrated into wallets including cross-chain swap aggregators and several major exchange front-ends.
​

Axelar's 2024 roadmap centered on the Mobius Development Stack (MDS), a set of upgrades that loosen Axelar's earlier dependency on its own L1 for every cross-chain operation. MDS introduced Amplifier, a permissionless framework that lets new chains plug into the Axelar network by deploying their own verifier contracts and registering them with the Axelar gateway. Before Amplifier, every new chain had to be supported by the full validator set; with Amplifier, the chain operator deploys verifier logic that the validators read on demand.
​

The change makes Axelar more competitive on chain coverage. A new appchain or rollup that wants Axelar GMP support no longer needs every validator to run a chain agent for that environment — the chain provides the verifier code, and validators evaluate the verifier output. As of April 2026 several Movement Labs chains, Stellar's Soroban environment, and the XRPL EVM sidechain have onboarded through Amplifier rather than the legacy validator-coordination flow.
​

MDS also introduced ITS Hub, a unified registry that lets a token issuer manage Interchain Token Service deployments across all connected chains from a single Axelar-side configuration. Issuers can update token metadata, change rate limits, and pause specific lanes without touching the per-chain contracts. The hub is documented in Amplifier's introduction documentation.
​

For protocol-level security comparisons, see cross-chain messaging security models compared. For deeper coverage of LayerZero and Wormhole, see the Wormhole vs LayerZero comparison.
​

Five production deployments illustrate how Axelar GMP shows up across different application categories.

The common pattern is that GMP is invisible to end users. Squid users see a swap; Microsoft pilot users saw a settlement; Frax users see a mint. The cross-chain mechanics are abstracted by the application layer, with Axelar handling the validator coordination and gas conversion underneath.
​

Eco Routes' selector treats Axelar GMP as one of the available transport rails for routes where Axelar's chain coverage and gas-abstraction model are the right fit. For applications that want a single rail with consistent slashing-backed validator economics across the entire connected chain set, Axelar is a natural choice; the Routes selector picks it for those routes.
​

The orchestration sits above the rail. An application integrating Eco Routes does not need to deploy an Axelar Executable contract, configure ITS pools, or manage AXL gas. Routes handles those details when Axelar is the chosen rail and falls through to LayerZero, Hyperlane, or CCTP when those are better fits. Builders looking for a higher-level introduction can read the cross-chain messaging primer or the cross-chain messaging pillar.
​

Axelar is a generalized message-passing network, not a specific bridge. It moves arbitrary contract calls between chains, with token transfers being a special case implemented through Interchain Token Service. A regular bridge usually only handles a fixed set of assets and does not expose function-call payloads.
​

The Gateway is a smart contract deployed on every Axelar-connected chain. It serves as the entry point (callContract) for outbound messages and the verifier (execute) for inbound messages. Validators sign attestations that the Gateway checks before delivering payloads to destination contracts.
​

Validators vote on cross-chain event validity with weight equal to the square root of their stake, not raw stake. This dampens the influence of large validators and rewards broader participation. It is one of the security mechanisms that distinguishes Axelar from validator-set protocols using linear stake weighting.
​

The Axelar Gas Service lets users pay destination-chain gas in any token Axelar accepts on the source chain. A user sending a message from Ethereum to Solana can pay Solana's execution gas in ETH; Axelar Relayers convert the prepayment into SOL when delivering. This removes the need for users to hold gas tokens for every chain they interact with.
​

Axelar has not had a verification-layer exploit since launching mainnet in 2022. The protocol has had several minor incidents — a Squid Router front-end issue in October 2022 that was caught before exploitation, and a brief lane pause in 2023 — but no validator-set compromise or stolen funds tied to the messaging layer.
​