Token bridging protocols are systems that coordinate asset transfers or token representations between otherwise separate blockchains. An original token does not literally leave its blockchain: the bridge coordinates corresponding changes on the participating ledgers. This can make an asset available on another chain, including for use in compatible decentralized applications (dApps) and decentralized finance (DeFi) services.
How Lock-and-Mint Bridging Works
A common design used by token bridging protocols is lock-and-mint. Assets are deposited into escrow on the source chain, where they cannot circulate freely while their destination-chain representations remain outstanding. The bridge then verifies the deposit under its security model. Depending on the design, that verification may rely on operators, a validator group, or proofs checked by smart contracts.
Once the deposit is accepted, corresponding wrapped tokens are issued on the destination chain. These tokens represent the escrowed source assets rather than moving the originals onto a new ledger. The source asset may itself be a token issued by a smart contract; bridging is not restricted to a blockchain's native gas token. The wrapped token is a separate asset on the destination ledger, whose holders rely on the bridge to maintain its backing.
Redemption and Asset Backing
For token bridging protocols using lock-and-mint, redemption reverses the process. Wrapped tokens are burned on the destination chain, the bridge verifies the burn, and the corresponding escrowed assets are released on the source chain. Burning removes the representations from circulation before their backing becomes available again.
Redemption depends on intact backing and a functioning bridge, including its verification and release mechanisms. A wrapped token's claim to an equivalent quantity of the source asset does not guarantee an identical market price. Its functionality and usability can also differ because destination-chain applications may treat it differently.
Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?
Get startedBridge Designs and Verification
Token bridging protocols do not all use lock-and-mint. Some burn tokens on one chain and reissue them on another under a coordinated issuance system. Others deliver assets from liquidity already available on the destination chain. In those liquidity-based designs, the route depends on sufficient destination-side inventory rather than necessarily creating a new wrapped token for each transfer.
The trust model matters independently of the transfer mechanism. An exchange-mediated transfer relies on the exchange, while a bridge relies on its particular contracts, verification system, and any custodians or operators. A protocol can use smart contracts yet still depend on a small group controlling approvals or escrowed assets. Neither the bridge label nor decentralization alone establishes greater safety.
Practical Limits and Risks
Token bridging protocols support specific assets and routes, not arbitrary transfers between any two chains. The destination application must support the exact token received, not merely an asset with the same name or symbol. Bridging is not limited to Ethereum, and compatibility with the Ethereum Virtual Machine (EVM) does not by itself establish a working or secure bridge. Fees and completion times vary with the route, network conditions, and verification requirements.
Contract flaws, compromised verification systems, or failures of custody can cause loss, frozen funds, or unbacked representations. A visible destination-chain balance therefore does not establish that redemption remains possible. Liquidity shortages can limit transfer sizes, delay execution, or prevent a route from completing in designs that depend on pools or other liquidity sources. Those constraints are design-specific: not every bridge requires a liquidity pool.
