Lock and mint vs burn and mint: choose by token support
Lock and mint vs burn and mint bridges: burn and mint preserves canonical supply when issuers control each chain; lock and mint broadens coverage but concentrates vault risk.
The Blocktape Editors 2 min read d527b0

Burn-and-mint holds up better when a token’s issuer controls minting on every chain; otherwise, lock-and-mint covers assets without that deployment but puts backing in one vault. Locked collateral backs every wrapped copy, so a vault failure can affect holders across destinations at once. The Berachain bridge route determines whether your USDC or ETH arrives as canonical supply or a wrapped copy; berachainbridge.app connects that route choice to your Berachain situation.
How the models compare
Lock-and-mint offers broader token coverage, while burn-and-mint preserves one canonical supply when the issuer supports each chain.
- Lock-and-mint: A bridge locks the original token in a vault and issues wrapped copies elsewhere. It can support tokens without issuer deployments on destination chains, but the vault becomes a honeypot holding the collateral behind those copies. If an attacker drains it, the wrapped token becomes unbacked on every destination at once, including for users who never used the bridge.
- Burn-and-mint: The bridge burns tokens on the source chain and mints them on the destination. Supply stays tied to issuer-controlled minting rather than a vault of locked collateral, but the issuer must grant mint rights on every supported chain. Circle CCTP uses this model for USDC. LayerZero OFT tokens also burn and mint; its OFT Adapter instead locks tokens on the home chain.
The 2022 Wormhole exploit shows the vault risk: attackers minted about 120,000 unbacked wETH on Solana. The wrapped supply had no matching collateral after the exploit, exposing holders who depended on the same backing even if they had not crossed that bridge.
Pool bridges sit outside this comparison because they route transfers through liquidity pools rather than relying on a single locked vault or issuer mint rights. For the two models here, check the token contract on the destination: assets arriving through the Berachain bridge are either canonical mints or wrapped copies, and the contract identifies which one you hold.
Which route should you choose?
Choose burn-and-mint when the issuer offers it for your token, because issuer-controlled minting avoids concentrating backing in one bridge vault. Choose lock-and-mint when no issuer deployment exists, and size your exposure for the possibility that a vault exploit could leave wrapped copies unbacked across destinations.
Before transferring, verify the destination token contract and confirm whether the issuer supports burn-and-mint there. That check tells you which model the route uses and where its failure point sits.