Axelar Network: Connecting Applications with Blockchain Ecosystems

Document Axelar Network: Connecting Applications with Blockchain Ecosystems, Draft 1.0
Authors No individual authors are listed on the paper’s title page
Year 2021
Project Axelar Network
License Not stated in the source
Official Source Axelar Network: Connecting Applications with Blockchain Ecosystems (Draft 1.0, PDF)

Disclaimer: This page is an educational summary of a 2021 protocol proposal and current public documentation. The paper describes a design; it does not by itself establish which features or parameters are deployed today. Cross-chain systems add technical and operational risks. This is not investment, legal, or financial advice.

Original paper Original paper
Directories Ethereum Whitepapers & Research

What the 2021 Paper Proposed

Axelar Network: Connecting Applications with Blockchain Ecosystems is a Draft 1.0 proposal dated January 2021. It describes a network intended to help applications send information and value between otherwise separate blockchains. The paper calls its two main protocol layers the Cross-Chain Gateway Protocol (CGP) and the Cross-Chain Transfer Protocol (CTP). Those are the paper’s names and architecture; current Axelar documentation uses General Message Passing (GMP) for its cross-chain application messaging product.

CGP is the routing layer: it connects chain gateways and carries verified information between networks. CTP is the application layer: it lets an application request an action, such as transferring an asset or triggering a contract on another chain. Put simply, CGP is about getting a message to the right network, while CTP describes what an application wants done with it.

Gateways, Validators, and Threshold Keys

The proposal describes Axelar as a proof-of-stake network with a validator set. Validators observe events on supported external chains, agree on what happened, and collectively authorize actions through threshold cryptography. A gateway on a connected chain receives an approved cross-chain instruction. The private signing key is split into shares, so a single validator does not hold the whole key. The paper describes separate questions that must both be answered: did the source-chain event happen, and have enough authorized key shares signed the resulting command?

The paper’s proposed security parameters need a date attached. It describes a 90% safety threshold for the design and an emergency-unlock recovery mechanism if the network stalls; it also says the final deployment parameter could change. These are historical design proposals, not evidence that the current service uses the same threshold or recovery arrangement. Current Axelar documentation describes quadratic voting for cross-chain event validation, where voting weight is proportional to the square root of stake, while block production and rewards use standard stake-weighted proof of stake. It separately describes gateway actions as requiring a threshold of validator key shares. Do not collapse these mechanisms into a single “two-thirds signs every message” rule.

How Current GMP Works

In the current documented flow, an application calls an Axelar Gateway on a supported source chain. The gateway emits a message event. A relayer submits that event for validation, Axelar validators vote on whether it is authentic, and enough key-share holders authorize the destination command. Relayers can then submit the signed approval to the destination gateway, which checks it before a destination application executes the payload. A gas service can collect fees on the source chain to cover work across the route; underfunded or incompatible calls may need monitoring or recovery.

GMP can carry a contract call, and some flows can attach tokens. It is not an unrestricted instruction to call any contract anywhere: both chains need supported Axelar gateways, the destination application must be deployed and able to process the call, and support varies by chain and feature. Axelar’s documentation also warns that an application inherits risks from the chains and contracts it integrates with. A convenient message API does not remove the need to review destination code, asset representations, fees, and failure handling.

Trust Assumptions and Limits

Axelar and Inter-Blockchain Communication (IBC) take different approaches. Axelar’s documented route relies on Axelar validators to vote on observed source events and on threshold key shares to authorize actions at a gateway. IBC light clients verify another chain’s headers and proofs under that chain’s consensus assumptions. That distinction matters, but it does not make IBC independent of validator or consensus security: each connected chain still has its own security model, and applications must check the specific client, connection, and contract behavior they use.

Neither model makes every cross-chain application safe by default. A bug in a destination contract, an incorrectly configured connection, a compromised chain, insufficient destination gas, or a faulty integration can create risks outside the abstract protocol design. A useful review separates network consensus, cross-chain validation, signing authorization, application code, and the behavior of each connected chain.

The 2026 Axelar–Secret Incident

A June 2026 incident shows why integration details matter. In its June 19 report, Secret Network said an attacker exploited the Secret-side ics20-for-axelar contract, which accepted messages from a counterfeit chain and minted unbacked Axelar-bridged tokens. Redeeming those tokens through the legitimate route then drained about $4.67 million from the associated Axelar escrow. Secret’s report said the affected contract and bridged assets were compromised, while the Axelar core protocol and unrelated Secret assets were not. This was not evidence that Axelar’s validator consensus itself was compromised; it was still a loss involving assets held in the Axelar bridge route, and it exposed failures in the integration and response safeguards. Secret said the connection had been paused as of that report; that dated statement does not establish its availability now.

Social Media Sentiment

A small Reddit discussion in r/Hedera about an Axelar-powered Squid Router connection included both a question about whether the new route duplicated an existing service or counted as a bridge and a reply describing lower friction for people already using Squid. This is a handful of comments about one integration, not a broad measure of opinion about Axelar or its security. It does illustrate why pages should distinguish the underlying interoperability network, an application router, and the user-facing route.

Last updated: 2026-10

Related Terms

See Also

Sources