How Cross-Chain Bridges Work While Your Tokens Are in Transit
How cross-chain bridges work: tokens are locked or burned, a source event is verified, and an equivalent amount is minted or released on the destination chain.
By The Token Trail Desk3 min read

A cross-chain bridge moves value by locking or burning tokens on one chain, verifying that event, then minting or releasing an equivalent amount on another. Each blockchain can read only its own state, so a verifier must relay signed proof between them. The Monad bridge is a clear case because its Ethereum-to-Monad route uses lock-and-mint.
A bridge turns a source-chain event into tokens on another chain
A bridge transfer has four stages:
- Source tokens are locked or burned.
- A verifier watches for the event and waits for finality, when the event is settled enough to rely on.
- The verifier signs proof and relays it to the destination chain.
- A destination contract mints or releases the corresponding tokens.
The proof connects the two chains. Ethereum cannot directly read Monad’s state, and Monad cannot directly read Ethereum’s. Instead, the destination contract checks the relayed proof before it releases or creates tokens. In a lock-and-mint transfer, the locked source tokens back the destination tokens. In a burn-and-mint transfer, the source tokens are destroyed and an equivalent amount is created on the destination.
Wormhole Guardians watch source-chain events and sign a VAA, or Verifiable Action Approval, once 13 of its 19 Guardians attest to an event. Wormhole Native Token Transfers supports both hub-and-spoke lock-and-mint and burn-and-mint modes. Axelar General Message Passing can relay arbitrary contract calls, so it handles more than token transfers.
An Ethereum-to-Monad transfer locks tokens before minting them
Say you send ETH from Ethereum to Monad through Monad bridge. The bridge locks the ETH on Ethereum and emits an event. A verifier set observes that event, waits for it to reach finality, and produces signed proof. The proof reaches Monad, where a contract mints a token against the Ethereum lock. Your wallet then shows the destination token; the ETH itself never left Ethereum.
The verifier set is the trust point. You gain a way to move value between chains that cannot check each other’s records, but that convenience depends on the verifiers correctly confirming the source event. If they are compromised, they may approve tokens without sound backing, putting the value represented on the destination chain at risk. For an occasional bridge user, the key trade-off is how much trust to place in that verification system.
Related
Are cross-chain bridges safe?
Bridge safety depends in part on how its verifier set works and whether destination tokens remain backed by source-chain assets. A compromised verifier can undermine that backing, so the bridge’s verification model matters alongside the transfer itself.
What is a wrapped token?
A wrapped token represents an asset from another chain. It may be the token you receive after a lock-and-mint transfer, but it is not automatically accepted by every app or exchange. The token contract address determines which DEXs and apps recognize it. Before trading, compare that address with the one the intended app supports; a familiar token name alone is not enough.
- Source tokens are locked or burned.
- Verifiers confirm the event and relay signed proof.
- The destination chain releases or mints an equivalent token.
- Check the received token’s contract address before trading.