The following is not a comprehensive list of Axelar's documentation. For full documentation and additional resources, please visit our Developer Docs.
|Developer Introduction Docs
Axelar enables secure interchain communication and token transfers, regardless of consensus mechanism or message payload.
Interchain apps built on Axelar are truly permissionless, meaning that their transactions cannot be censored by any oracle, relayer or validator. Axelar is based on the same proof-of-stake security model as many of the chains it connects.
|Interchain Token Docs
|Axelar has several ways to send supported native tokens, but what if you want to have your own ERC-20 token available on multiple chains? Axelar can help with Interchain Tokens!
Interchain Tokens are created and managed by our new Interchain Token Service, which allows you to send tokens cross-chain, build your own asset bridges, build asset transfers into your interchain dApp, and take on many other use cases. Deploy your Interchain Token today via our Interchain Portal.
|AxelarJS SDK & API Docs
|Anyone can view General Message Passing calls and check the GMP transaction status in realtime on Axelar's block explorer Axelarscan.
|General Message Passing Docs
Axelar’s General Message Passing (GMP) enables a developer building on one chain to call any function on any other connected chain. (We use the word “function” to encompass both smart contracts at the application layer and functions built at the protocol layer, as in Cosmos, for example.) That means complete composability across Web3.
There are two ways to disclose security vulnerabilities to the Axelar team:
Even if your security vulnerability is not eligible for a bounty from the bug bounty program (option 1) the Axelar team might decide to award a bounty for a security vulnerability submitted by email to