Axelar RPC: Connecting to the Cross-Chain Messaging Layer

Axelar is one of the major cross-chain interoperability networks, and it's easy to misunderstand if you arrive expecting an EVM chain — because it isn't one. Axelar is a Cosmos SDK proof-of-stake network whose whole job is connecting other blockchains: moving tokens and arbitrary messages between them. Once you understand that, its RPC makes sense. Here's the map.

What Axelar actually does

Most blockchains are islands. Axelar's purpose is to be the communication layer between them, built around two primitives:

• Cross-chain token bridging: move a token from one connected chain to another. Axelar locks or burns on the source, mints or releases on the destination, coordinated by its validator set.
• General Message Passing (GMP): a contract on one chain calls a function on a contract on another chain, passing arbitrary data along with it. This is what makes cross-chain applications possible, not just token transfers.

The mechanics: Axelar's validators run light clients of the connected chains and watch for events. When something happens on a source chain, the validators collectively attest to it using threshold signatures, and that attestation authorizes the corresponding action on the destination chain. Axelar launched mainnet in February 2022, is built with the Cosmos SDK + CometBFT (Tendermint) consensus, uses the AXL token (6 decimals) for staking, fees, and governance, and produces ~6-second blocks with single-block deterministic finality.

The RPC reality: it's a Cosmos chain, not an EVM one

Because Axelar is a Cosmos SDK chain, you don't talk to it with eth_* — those methods don't exist here. You use the CometBFT (Tendermint) RPC, the same consensus-layer RPC every Cosmos chain exposes. SwiftNodes serves this endpoint:

# Node + sync status (CometBFT RPC)
curl -s -X POST https://rpc.swiftnodes.io/rpc/axelar?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"status","params":[],"id":1}'
# -> {"result":{"node_info":{...},"sync_info":{"latest_block_height":"...",...}}}

The CometBFT RPC methods you'll actually use:

If you're new to the Cosmos RPC stack — how Tendermint RPC relates to the REST (LCD) and gRPC interfaces — we cover the whole thing in our Cosmos RPC explainer. The same surface applies across Celestia, Osmosis, and the rest of the Cosmos family.

Where the special part lives: GMP and cross-chain messages

The thing that makes Axelar Axelar — the actual cross-chain messaging — doesn't happen over a special RPC method. It's driven by smart contracts on the connected chains calling into Axelar's gateway contracts, with Axelar's validators relaying and attesting the messages between them. From your RPC's point of view, cross-chain activity shows up as ordinary Axelar transactions and events you read with block_results / abci_query — the cross-chain magic is coordinated by the validator set, not exposed as a bespoke endpoint.

The practical split for a developer:

• To read or index Axelar itself — track GMP message status, watch validator attestations, monitor bridging activity — use the CometBFT RPC. That's what a flat-rate endpoint like SwiftNodes gives you.
• To initiate a cross-chain call — you interact with Axelar's gateway contract on your source chain (e.g. an EVM chain), using its SDKs. Axelar's own RPC is where you observe and verify the result.

Finality and reading the chain

Axelar has single-block deterministic finality via CometBFT — once a block is committed by the validator set, it's final, no reorgs. One nuance for cross-chain builders: delivery on the destination chain also depends on that chain's own finality, so an end-to-end GMP call is only as final as both ends. For indexing Axelar itself, though, you can trust a committed block immediately — no probabilistic confirmation waits, minimal reorg handling. Read blocks and results via block / block_results, and query state via abci_query.

The short version

Axelar is a cross-chain interoperability network, not an EVM chain — so its RPC is Cosmos CometBFT (Tendermint) RPC, not eth_*. Use status, block, block_results, abci_query, and broadcast_tx_* to read state and broadcast transactions. The cross-chain part — token bridging and General Message Passing — is coordinated by Axelar's validator set via threshold-signed attestations; you initiate cross-chain calls from your source chain's gateway contract and observe them on Axelar. Single-block BFT finality means reads are deterministic.

For reading Axelar, tracking GMP activity, and broadcasting transactions, you need a reliable CometBFT endpoint. A flat-rate Axelar RPC endpoint gives you that across load-balanced nodes, alongside dozens of other chains under one key. Grab a free key and point your app at:

https://rpc.swiftnodes.io/rpc/axelar?key=YOUR_API_KEY