Skip to the article
Blockheight

Crypto markets, protocols, policy

Lock-and-mint bridges: how tokens cross chains

How does lock and mint bridging work? The source tokens are locked, then validators relay a message so an equal representation can be minted on the destination chain.

The Blockheight Editors··3 min read

Lock-and-mint bridges: how tokens cross chains

After a lock-and-mint transfer, your source tokens stay in a bridge contract while an equal representation is minted on the destination chain. Gnosis Bridge is a concrete example: its Omnibridge locks ERC-20s on Ethereum and mints bridged tokens on Gnosis Chain. The supply is created when needed, so the output has no pool price curve; fees can still reduce what arrives.

Omnibridge locks tokens, then validators relay a mint message

For an Ethereum-to-Gnosis transfer, Omnibridge first receives the approved ERC-20s in its Ethereum contract. That contract sends a message through the Arbitrary Message Bridge (AMB), which is monitored by bridge validators. Once enough validators attest to the transfer, the destination contract mints the corresponding bridged tokens on Gnosis Chain. Gnosis Chain’s Omnibridge documentation describes this sequence.

In the reverse direction, Omnibridge burns the bridged tokens on Gnosis Chain and relays a message to unlock the original tokens on Ethereum. The lock and mint, then burn and unlock, keep the two supplies tied together. The AMB carries the message; validators attest to it before the destination contract acts.

That process also explains the wait: the destination mint or unlock depends on source-chain confirmation, validator signatures and message execution. The Gnosis Chain docs say the AMB and Omnibridge share a validator set, so the bridge relies on those validators as well as the contracts on both chains.

Lock-and-mint avoids pool slippage but gives you a bridged token

A pool bridge uses inventory already available on the destination chain. It swaps or releases that inventory to the user, so the amount received can depend on pool balances and the route’s price impact. Lock-and-mint instead creates the destination representation from the amount locked, typically 1:1 before fees. There is no price curve, so a slippage tolerance setting does not change the quoted token amount. Ethereum.org’s bridge overview distinguishes lock-and-mint from liquidity-based routes.

For a large transfer, that difference is practical: a pool route may deliver less as the trade moves through available liquidity, while a lock-and-mint quote is not reduced by price impact. Compare the bridge fee, both chains’ gas costs, and the time needed for confirmation and relay. Symbiosis and Bungee can route cross-chain swaps; check the route details to see whether the path uses pool liquidity and what output it quotes.

The destination token in a lock-and-mint route is a bridge-specific representation, not automatically the same asset contract as the native token on that chain. You take on bridge contract and validator risk, and you need a route back that can burn the representation and unlock the original. Gnosis Bridge is one example of this model: Omnibridge uses AMB messages to connect the lock on Ethereum to the mint on Gnosis Chain.

Two checks before choosing a bridge

Are wrapped bridged tokens the same as native tokens?

No. A wrapped bridged token is a separate representation backed by tokens locked elsewhere; its value depends on the bridge and its ability to redeem the backing asset.

Which bridge is cheapest for large transfers?

There is no fixed winner. Compare the lock-and-mint fee and gas with the pool route’s quoted output, price impact and gas; the cheapest route depends on the token, amount and current liquidity.

Related stories