Skip to main content
Chain Media

Protocols, chains and markets, reported

Monad bridge transfer methods: know what each route changes

Monad bridge transfer methods include lock-and-mint, burn-and-mint, pools and intent routes, each trading speed, fees, trust and the token you receive.

The Chain Media Editors5 min read

Monad bridge transfer methods: know what each route changes

Monad bridge transfers can route through lock-and-mint, burn-and-mint, liquidity pools or intent relayers, with aggregators selecting among them. Each route changes how assets reach Monad from Ethereum, how quickly they arrive and what token the recipient holds.

Four routing models

Lock-and-mint: keep the original on Ethereum

Lock-and-mint holds an asset in a contract on Ethereum and issues a wrapped representation on Monad. The wrapped token tracks the locked asset, but it is a distinct token on the destination chain. This route suits someone who accepts that distinction and wants a bridge representation backed by the asset held on Ethereum. Redemption depends on the bridge releasing the locked asset when the wrapped version is returned or burned.

Burn-and-mint: carry the issuer’s token across chains

With Native Token Transfers (NTT), an issuer can burn its token on the source chain and mint the corresponding token on the destination. Wormhole NTT supports this burn-or-lock source action followed by minting on the destination. The route can preserve the token’s native identity across chains, provided the issuer has configured support for both chains and the asset.

Illustrative case: before a transfer, a user holds an issuer’s native token on Ethereum; afterward, the user holds that issuer’s native token on Monad. The balance has moved chains, but the asset identity stays the same. In a burn-and-mint route, source units are burned and destination units are minted. This suits users who value receiving the issuer’s canonical token, with trust placed in the issuer’s cross-chain setup and its controls.

Liquidity pools: receive tokens already on Monad

A liquidity-pool route pays out tokens already held on Monad instead of minting a wrapped representation there. Stargate is an example of a pool-based design where supported. The source asset funds the route, and destination liquidity supplies the payout. This can make the destination transfer straightforward, but pool depth and route availability affect what can be paid out. The token received may be the pool’s destination asset rather than a wrapped copy of the exact source token.

Intent and relayer: trade a fee for speed

An intent route lets a user specify the desired outcome while a relayer fulfills it on the destination side. Across uses relayers that front funds on the destination and are repaid later. That means the user can receive the destination funds without personally waiting through the full source-chain finality period. The wait still exists in the system: the relayer takes it on and prices that service into the fee, often through a spread.

Where available, intent routes such as Across and deBridge are the fastest of these models from the user’s perspective. The gain is a quicker destination payout; the cost is the relayer’s spread and reliance on the route’s fulfillment and repayment process. Speed matters most when waiting is costly. For a user prioritizing the issuer’s canonical token, the issuer’s burn-and-mint route may matter more.

How to compare a route

Before choosing, compare speed, fee, trust assumptions and the token received. A bridge aggregator can select among routes using those trade-offs, while a direct bridge exposes a particular route or set of routes. An aggregator can add its own fee, but the total can also reflect the underlying route, liquidity, relayer spread and transaction costs. Compare the quoted destination amount and route details when they are available.

Messaging layers sit underneath some asset routes. Axelar General Message Passing (GMP) carries instructions between chains; another component or application can use that message to trigger the asset action. GMP is therefore a messaging layer, not itself a synonym for lock-and-mint, a pool payout or an intent. Identifying both layers helps explain what moves the instruction and what actually provides the destination asset.

Is Monad bridge the same as Portal Bridge?

No. “Monad bridge” refers to the cross-chain app for transferring supported assets between Monad and Ethereum; Portal Bridge is a Wormhole bridge interface. The names describe different things: one identifies the app in this context, while the other names a Wormhole product. A route’s actual mechanism still depends on the specific transfer path.

Fastest way to bridge ETH to Monad

An intent route is designed to feel fastest because a relayer can front funds on Monad while Ethereum finality completes in the background. That speed usually costs a relayer spread, and the available route and ETH support depend on the options offered at transfer time. A pool or mint-based route may suit a user who values the resulting token or trust model more than early payout.

Bridge aggregator vs direct bridge

An aggregator compares or selects routes across available bridge mechanisms; a direct bridge uses a particular provider’s route. Aggregation can make route choice easier, but the user should still identify the underlying model, destination token and total quoted cost. The provider name alone does not tell you whether the transfer uses locked collateral, token burning, pool liquidity or a relayer.

The Monad bridge is the cross-chain app at the center of this comparison: understanding its available route means asking which mechanism moves value between Ethereum and Monad. Choose an intent route when payout speed outweighs the spread; choose the issuer’s burn-and-mint route when receiving its canonical token is the priority.

More questions

Which route does the official Monad bridge use for MON?

The route depends on the bridge’s current MON configuration. The route model should be identified from the transfer option itself; the app’s name alone does not establish whether MON is locked and wrapped, burned and minted, paid from a pool or fulfilled by a relayer.

Do aggregators add their own fee on top?

They may. The total can include an aggregator charge as well as the underlying bridge fee, pool price impact, relayer spread and chain transaction costs. Compare the final quoted amount and any fee breakdown for the selected route.