Axelar Documentation
website·Indexed 34 days ago
https://docs.axelar.dev/Developer guides and technical documentation for the Axelar network, featuring General Message Passing (GMP), the Interchain Token Service (ITS), and the AxelarJS SDK. Includes instructions for node configuration, validator onboarding, chain integration via the Axelar Amplifier, and gas estimation for cross-chain transactions.
What's inside Axelar
- Axelar General Message Passing (GMP) allows developers to build interchain-native applications that perform cross-chain function calls and synchronize state between EVM and Cosmos ecosystems. On Cosmos chains, messages can be received by CosmWasm smart contracts or natively at the consensus layer via Go code. The mechanism utilizes IBC's memo field to transport messages.
Overview of Verifier Rotations
Verifier rotations allow the network to update the set of verifiers for a specific chain. To implement an update, the previous verifier set must sign a message communicating the changes to the destination chain.Overview of Axelar Amplifier Verifier Rewards
Verifiers earn rewards for securing transactions on chains connected to the Axelar Network. Rewards are provided by chain integrators and are based on contributions tracked in the verifier rewards contract. A contribution is counted when a verifier votes in a poll or signs an event. Rewards are assessed per epoch (a governance-configured time window) and paid in AXL based on a percentage of the chain's traffic.Overview of Custom Token Integration with Axelar ITS
Custom tokens are independently deployed ERC-20 tokens (as opposed to InterchainTokens deployed via the ITS). To make a custom token bridgeable across blockchains, a Token Manager must be deployed for the token on each chain. Tokens become bridgeable when they are connected to Token Managers that share the sameinterchainTokenId.Overview of the Coin Management module
The
Coin Managementmodule is a core component of the Interchain Token Service (ITS) on Sui. It must be created before a coin is registered with ITS. It handles minting, burning, balance management, and flow limits for cross-chain operations.Key fields in the
CoinManagementstructure include:treasury_cap: Optional capability for minting/burning.balance: Optional balance for locked coins.distributor: Address authorized for minting/burning.operator: Address authorized to set flow limits.flow_limit: Tracks allowed inflow and outflow.dust: Tracks leftover coins after transfers.
public struct CoinManagement<phantom T> has store { treasury_cap: Option<TreasuryCap<T>>, balance: Option<Balance<T>>, distributor: Option<address>, operator: Option<address>, flow_limit: FlowLimit, dust: u256, }Overview of Axelar Solana Integration
Solana is integrated with the Axelar Network via the Amplifier, enabling cross-chain communication. Axelar provides two primary protocols for Solana developers:
- General Message Passing (GMP): Used to send and receive arbitrary cross-chain messages between Solana programs and contracts on other supported blockchains.
- Interchain Token Service (ITS): Used for cross-chain token transfers, including deploying interchain tokens, registering canonical tokens, and linking existing tokens across chains. ITS can optionally include execution data with transfers.
Overview of the Interchain Amplifier
The Interchain Amplifier is a set of on-chain contracts and services within the Axelar Mobius Development Stack (MDS) that allows integrators to connect new blockchains and services to the Axelar network. It enables generalized connections between chains regardless of their technology stack (e.g., Solidity, Rust) or consensus mechanism (e.g., PoS, L2s). The Amplifier consists of an on-chain message router, gateways, and CosmWasm methods for sending and receiving messages.Overview of the Solana Axelar Gateway
The Solana Axelar Gateway is a Solana program that acts as the authentication layer for General Message Passing (GMP). It enables cross-chain communication by verifying that incoming messages are signed by Axelar's verifier set and providing the mechanism to send outbound messages to other chains.Overview of the Axelar Interchain Token Service (ITS)
The Interchain Token Service (ITS) enables ERC-20 tokens to be available on multiple blockchains as canonical versions that share a single EVM address. Unlike legacy bridges, ITS preserves native token qualities and allows developers to manage token features and supply across chains using open-source smart contracts secured by a dynamic validator set.Overview of Flow Limit in Interchain Token Service
TheFlowLimitcontract ensures the stability and security of interchain operations by constraining the volume of tokens that can be transferred within a specific time frame (an epoch). This prevents system abuse, overload, and can be used to halt transfers during emergency situations on a specific chain. TheTokenManagercontract utilizesFlowLimitto regulate the volume of tokens entering and leaving a blockchain.Overview of Canonical Interchain Tokens
A Canonical Interchain Token is an ERC-20 token registered via the InterchainTokenFactory contract to enable interoperability across different blockchains. This process allows developers to create wrapped, bridgeable versions of their token on other chains. A critical constraint is that each token can only be registered once as a Canonical Interchain Token to ensure unique token management across the network.Overview of the Axelar EVM Relayer
The Axelar EVM relayer enables communication between EVM-compatible chains. It supports both legacy and EIP-1559 transaction types. The system uses relayer queues as entry points, with multiple relayer instances running in parallel to process messages. If a process is interrupted, an internal database recovers the payload for retry. The core relayer workflow consists of three steps: receiving a payload (containingto,value, anddata), querying gas fees and prices, and broadcasting the transaction.