Wormhole vs Axelar for Monad Transfers: How Routes Differ
Wormhole vs Axelar for bridging to Monad: the token issuer’s framework decides the canonical route; compare received amounts and delay when several routes exist.
Crypto Daybook Newsroom3 min read
Wormhole vs Axelar for moving tokens to Monad comes down to the token’s issuer: use the framework that issuer deployed, because it delivers the canonical token on Monad. Wormhole uses Native Token Transfers (NTT), while Axelar uses its Interchain Token Service (ITS); the two routes verify messages differently.
Before you send, find the token’s supported route in the app you plan to use. Monad bridge may route through either layer depending on the asset, so check which one it uses for your token. For another option, compare the monad bridge alternatives when checking routes for Monad bridge.
How do Wormhole and Axelar verify a transfer?
Wormhole’s 19 Guardians observe messages and sign them. A Verifiable Action Approval (VAA), the proof sent to the destination chain, needs 13 signatures. A relayer submits the signed VAA to Monad; this route does not pass through the Axelar chain. Wormhole’s Guardian documentation describes the 13-of-19 quorum.
Axelar routes a General Message Passing (GMP) call through its own proof-of-stake chain. Validators check that the source-chain message happened, approve it, and sign the destination approval. A relayer carries that approval to Monad, where the destination gateway checks it before execution. Axelar’s message-flow documentation lays out those steps.
The token framework determines what arrives. With NTT, an issuer deploys its token across chains as a native token. With ITS, Axelar connects token deployments across chains. Sending an NTT token through an Axelar route can create or deliver a non-canonical version on Monad; an Axelar ITS token needs its Axelar route to arrive as the intended token.
Which route should you choose for your token?
Say two tokens have the same name and amount on Ethereum, and both show a Monad route. The first was deployed through NTT; choose Wormhole to receive its canonical Monad version. The second was deployed through Axelar ITS; choose Axelar for its canonical version. Only the issuer’s framework changed, so the matching route changed too.
For ETH or an asset with several supported routes, compare the amount you will receive and the estimated delay before confirming. To follow a Wormhole transfer, search its transaction in Wormholescan. For an Axelar transfer, use Axelarscan to view its GMP status, including approval and execution.
Related
Is Wormhole safe to use for Monad?
Wormhole uses a 13-of-19 Guardian signature quorum for its VAAs. Confirm that the token’s route is the issuer’s NTT deployment before sending.
Which explorer tracks an Axelar transfer?
Axelarscan tracks Axelar GMP calls. Search by transaction hash to see whether the message was approved and executed.