Axelar axl

Axelar is a decentralized interoperability network and development platform for connecting applications and assets across heterogeneous blockchains. Its official documentation describes the goal as secure cross-chain communication for interchain dApps, allowing users to interact with assets and applications on different chains in a unified experience. The network combines an Axelar proof-of-stake blockchain, validator-operated gateways on connected chains, relayer services, and developer APIs.

Axelar’s original whitepaper frames the protocol as a decentralized network, protocol suite, tools, and APIs for cross-chain communication. It defines a Cross-Chain Gateway Protocol (CGP) for routing between autonomous blockchain ecosystems and a Cross-Chain Transfer Protocol (CTP) for application-level asset transfers and cross-chain requests. The current product documentation also emphasizes General Message Passing (GMP), which lets an application call a contract on another chain.

AXL is the native token of the Axelar network. It is used to stake and secure consensus, delegate voting power to validators, pay network-related fees, and participate in governance. Validator stake also determines the amount of key-share weight used in the multi-party cryptography that controls Axelar Gateway contracts.

The network is not a single centralized bridge: validators jointly observe source-chain activity, vote on whether a request is valid, and collectively authorize destination-chain execution. This design makes Axelar a general-purpose interchain coordination layer rather than a bridge for only one asset pair.

Blockchains are fragmented: each chain has its own execution environment, consensus, assets, and addresses, so an application on one network cannot natively call contracts or access liquidity on another. Pairwise bridges require bespoke integrations for every chain pair, increasing engineering cost and creating a patchwork of trust assumptions. Users consequently face wrapped assets, separate wallets and liquidity pools, multiple transaction steps, and chain-specific gas requirements.

Axelar addresses the integration and trust problem with a universal routing and messaging layer. Developers can deploy an application on the chain best suited to it while using a common cross-chain interface. Validators verify events on source chains and threshold-authorize commands on destination chains, reducing reliance on a single bridge operator. The model still depends on validator economics, correct external-chain observation, Gateway smart-contract security, relayers, and the security assumptions of each connected chain; it does not eliminate interoperability risk.

A connected chain has an Axelar Gateway contract (or an equivalent threshold account for non-EVM chains). The Gateway is controlled jointly by Axelar validators through multi-party cryptography: the signing key is split into key shares, weighted according to validator stake, and a command executes only after the configured authorization threshold is reached.

For a cross-chain message or token transfer, a user or application initiates a request on the source chain. A relayer starts the corresponding confirmation vote on Axelar. Validators run or observe source-chain nodes, independently check whether the transaction occurred, and vote on the Axelar chain. Once the weighted confirmation threshold is met, validators use their key shares to authorize the destination-chain command.

For General Message Passing, the approved payload is delivered to the destination Gateway and then executed against the destination contract. The destination execution requires gas; an application can operate its own relayer or use Axelar’s Gas Receiver, which accepts payment on the source chain and enables relayer execution on the destination. For token transfers, Axelar’s Gateway flow can mint/burn or release the appropriate representation after the source event is confirmed.

AXL holders can delegate stake to validators or operate validators subject to network rules. The official staking guide denominates AXL in uaxl (1 AXL = 1,000,000 uaxl), requires at least 1 AXL to participate in consensus, and notes that validators need sufficient stake for the active set and may need additional stake for multi-party cryptography participation. Governance is used for network decisions such as supported chains and protocol changes.