How to follow a Monad bridge transfer from start to finish
How does Monad bridge work? A source contract locks or burns assets, a messaging layer attests to the transfer, and a destination contract releases or mints them.
The Chain Times Desk3 min read

Monad bridge moves assets between Ethereum and Monad when a source-chain contract locks or burns tokens and the destination contract accepts a verified message. Read Monad bridge for more on how the bridge to Monad moves assets from Ethereum. The message matters because Ethereum and Monad cannot read each other’s state directly; signed proof carries evidence of the source-chain transfer.
How does Monad bridge move tokens?
A bridge transfer passes through the source contract, a finality check, an attestation, a relayer, and the destination contract. Each stage leaves a different state behind.
- You start with tokens on Ethereum, such as ETH or a supported asset. Your wallet asks the source contract to transfer them.
- The source contract locks the tokens or burns them, then emits a message describing the transfer. The tokens are now locked or removed from that chain’s supply.
- The messaging layer waits for the source transaction to reach finality, then signs or validates its message. Wormhole produces a VAA, a signed attestation; Axelar validates a GMP call through its proof-of-stake validator set.
- A relayer submits that proof on Monad. The destination contract verifies it, then releases tokens held there or mints matching tokens. The assets are now available on Monad.
Monad is EVM-compatible, and MON is its native gas token. The bridge message handles the cross-chain proof; it does not make the two chains share a single transaction state.
Who secures a bridge to Monad?
The attestation set secures the cross-chain claim that tokens were locked or burned. That is the key trust point: the bridged token relies on the group signing or validating the message, not on Ethereum’s or Monad’s consensus alone.
For Wormhole, 19 Guardians form the attestation set, and 13 signatures are needed to create a VAA. Axelar GMP messages are validated by Axelar’s proof-of-stake validator set. These are different ways to attest to a source event; the route’s contracts and messaging design determine which trust assumptions apply.
The token model also matters. Wormhole Native Token Transfers (NTT) supports burn-and-mint as well as hub-and-spoke locking. Burn-and-mint keeps one token supply across chains: tokens burned on the source chain are minted on the destination. Lock-and-mint leaves value in a source-chain vault while corresponding tokens are minted elsewhere. That vault becomes a place where value is concentrated, so its security matters too.
What can make a transfer wait?
A transfer can wait for source finality, the attestation, or a relayer to submit the proof. Those are separate stages, so a delay at one does not mean the same thing as a delay at another.
In the Ethereum-to-Monad example, the source transaction may be complete while the attestation is still pending. After signatures or validation are ready, the transfer can still wait for relay and destination verification. Following those states helps locate the pause without treating “sent” as “received.”
Fees depend on the chosen route and its transactions; this pipeline alone gives no fixed fee. The main security question is which attestation set and contracts authorize the destination release or mint.