DEV Community

Mandie Brugman
Mandie Brugman

Posted on

Lock and Mint vs Burn and Mint Bridges: Safer for Holders

Burn-and-mint bridges usually leave holders with less risk when the token issuer controls the route. Burning the source token removes the locked pool that could be drained; lock-and-mint holders depend on that pool remaining intact. Burn-and-mint shifts the critical risk to who can authorize a mint and how the bridge verifies cross-chain messages.

Where Does Your ETH Sit After You Bridge It?

Under lock-and-mint, your ETH sits in a vault on the source chain while a wrapped token represents it on the destination chain. Each wrapped token is a claim on the ETH the vault holds.

This distinction matters when moving supported assets such as ETH and MON between Ethereum and Monad. The Monad bridge is a concrete place to examine it because its cross-chain transfers use Wormhole Native Token Transfers (NTT) infrastructure; the route for each asset determines whether tokens are locked or burned.

Consider an illustrative third-party lock-and-mint route. You deposit 1 ETH into its vault on Ethereum. After a cross-chain message is verified, the bridge mints 1 wrapped ETH for you on Monad. To return, you burn that wrapped ETH, and the bridge releases 1 ETH from the Ethereum vault. The wrapped token has value because that last step should remain possible.

If an attacker drains the vault, every holder of that wrapped ETH on Monad faces the same shortfall at once. A holder may still see the token in a wallet, but the bridge cannot redeem all claims for ETH. As more users try to sell or redeem, the wrapped token can trade below the asset it represents. The vault’s size is therefore part of the risk: transfers by many users accumulate in one place.

Burn-and-mint works differently. The issuer’s token is destroyed on the source chain, a verified message records the transfer, and the issuer-approved contract mints the same amount on the destination chain. There is no reserve of that token waiting in a bridge vault. On the return trip, the destination tokens are burned before the source tokens are minted again.

Who Can Mint the Token You Receive?

For burn-and-mint, the key question is who controls supply on both chains. The issuer must authorize the contracts that burn and mint its token. A third-party bridge cannot independently burn and recreate an issuer’s token; it generally has to lock the original and issue its own wrapped claim.

Burning removes vault theft from this route, but a compromised minter key or faulty message verification can still create tokens without a matching burn. That dilutes legitimate holders and can damage confidence in redemption. The 2022 Wormhole exploit shows why verification matters: an attacker exploited a Solana-side verification flaw and minted 120,000 unbacked wETH. Those tokens belonged to a wrapped-token bridge, and some were taken back to Ethereum to claim ETH from its reserves. Wormhole’s incident report describes the failure.

Wormhole NTT can put a limit on how much enters or leaves a chain over a period. When an inbound transfer exceeds the remaining limit, NTT queues it instead of minting immediately. An outbound transfer can also queue when that option is enabled. The delay gives operators time to detect an abnormal transfer and pause the route before queued tokens are released. It also delays an honest user whose transfer exceeds available capacity. Wormhole’s transfer documentation explains both checks.

That limit matters during a mint-key compromise only when the compromised authority must pass through the NTT manager to mint. In that setup, the configured inbound capacity caps how much an attacker can get minted through the route before more capacity becomes available. A separate key with direct permission to mint the token can bypass the NTT queue. The holder therefore needs to identify every minting permission, not just the bridge’s advertised limit.

Which Route Should You Choose on Monad?

Choose an issuer-approved burn-and-mint route over a third-party wrapped version when both exist for the same token. It avoids the shared vault that backs the third-party claim. Then inspect the issuer’s mint authority, message checks and active rate limits, because those controls carry the remaining supply risk.

Say you want to move an issuer’s token from Ethereum to use it in an app on Monad. The useful result is a token the app accepts without taking on an additional bridge’s reserve risk. Confirm the destination token contract the app accepts, then trace the route backward: was the Ethereum token burned, or is it still held in a vault? That source-chain action tells you which failure point supports the token you will hold.

Apply the same test on the Monad bridge rather than assuming every asset there follows one model. Wormhole NTT also supports a hub-and-spoke setup: tokens lock on their home chain, while tokens on other chains burn when they leave. A route using that setup still has a home-chain pool, even though a transfer between spoke chains involves burning. The token’s actual configuration determines the exposure.

Related Questions

What Is a Canonical Token?

A canonical token is the version an issuer recognizes for a chain. That designation helps you identify the intended contract, but it does not by itself tell you whether the transfer route burns tokens or holds a home-chain reserve. Look at the issuer’s route and mint permissions.

Can a Wrapped Token Lose Its Peg?

Yes. A wrapped token can fall below the original asset’s value when holders doubt that its backing can be redeemed. A drained vault creates a direct shortfall; unauthorized wrapped-token minting can create more claims than the vault can satisfy.

What Is a Hub-and-Spoke Bridge?

A hub-and-spoke bridge keeps the original token on a home chain and represents it on connected spoke chains. In Wormhole NTT’s version, the home-chain token locks when it leaves; spoke-chain tokens burn when they leave. Find the home-chain vault to locate the remaining pooled risk.

Top comments (0)