How Does a Burn and Mint Bridge Differ From a Lock and Mint Bridge?
A burn and mint bridge destroys tokens on the source chain and creates equivalent tokens on the destination chain, while a lock and mint bridge holds the original tokens in a smart contract and issues a representation on the other side. The key difference is where the original assets end up - they are permanently removed in a burn-and-mint design, versus held in custody in a lock-and-mint design.
The Lock and Mint Model: Custody of Original Tokens
In a lock and mint bridge, the original tokens never leave the source chain. You deposit them into a bridge contract that locks them - meaning they become unusable to you while the bridge holds them. A new, wrapped version of those tokens is then minted on the destination chain. The total supply of the original token on the source chain decreases temporarily (because the tokens are locked), and the wrapped token supply on the destination chain increases by the same amount.
When you want to return, the process reverses. The wrapped tokens are burned on the destination chain, and the bridge unlocks your original tokens on the source chain. The bridge contract acts as a custodian for the duration of your transfer.
This model is common for bridges that wrap native assets - for example, wrapping Bitcoin to use on Ethereum. The locked Bitcoin remains in a multisig-controlled contract, and the wrapped version (like WBTC) circulates elsewhere.
The Burn and Mint Model: Permanent Destruction of Original Tokens
A burn and mint bridge permanently destroys the original tokens on the source chain. The tokens are sent to a burner address - a contract with no private key and no withdrawal function - or are consumed by a function that reduces the total supply. The bridge then mints an equivalent amount of tokens on the destination chain. There is no locked reserve on the source chain.
When you bridge back, the process repeats: the tokens on the destination chain are burned, and new tokens are minted on the source chain. The total supply across both chains remains stable, but no single chain holds the original tokens in escrow.
This design is used by native bridges for blockchains that support native token burning, such as the Solana Wormhole bridge for SOL. It is also used by some layer-2 rollups that burn L1 ETH and mint L2 ETH.
Security implications of each model
Lock and mint risks center on the bridge contract holding large amounts of locked value. If the contract is exploited, the attacker can drain the locked tokens, leaving the wrapped tokens on the destination chain worthless. The bridge becomes a high-value target because the locked pool is a single point of failure. Multisig or quorum-based security councils are common protections, but they add centralization risk.
Burn and mint risks are different. Since no large pool of locked tokens exists on the source chain, a contract exploit cannot steal the underlying assets in bulk. However, the bridge must still correctly verify that the burn happened on the source chain before minting on the destination. If the verification mechanism - often a validator quorum or oracle - is compromised, the attacker could mint fake tokens on the destination chain without actually burning anything on the source. The result would be inflation of the destination token supply, which could crash its value.
Practical differences for users
When you use a lock and mint bridge, your original tokens are technically still yours - just locked. If the bridge pauses or gets hacked while your tokens are in transit, you might be able to recover them through the bridge's security council or a governance vote, depending on the design. With a burn and mint bridge, once the tokens are burned, they are gone. There is no way to retrieve them from the source chain. Your only hope is that the destination chain mint completes correctly.
Another practical difference is token recognition. Lock and mint bridges typically produce wrapped tokens that are distinct from the native asset - for example, "Wrapped ETH" on Arbitrum. Burn and mint bridges often mint the native token of the destination chain directly. For example, bridging ETH from Ethereum to Arbitrum via Arbitrum's native bridge burns L1 ETH and mints native Arbitrum ETH. The destination token behaves identically to ETH on Arbitrum, with no wrapping distinction.
Which model is more common
Lock and mint is the older, more widespread model. Most third-party bridges that wrap Bitcoin, Ethereum, or stablecoins use lock and mint because it allows the original tokens to remain on a chain where they are most liquid and trusted. Burn and mint is increasingly used by native bridges for blockchains that prioritize a unified token standard across their ecosystem - for instance, bridges between a layer-1 and its layer-2 rollups.
Neither model is inherently safer. The lock and mint model concentrates risk in a custodial pool; the burn and mint model shifts risk to the verification mechanism. Your choice should depend on which failure mode you consider more likely for a given bridge.
Not financial advice. basedbratt.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.