What Happens When You Bridge Crypto to Another Chain?

A crypto bridge moves value between blockchains by coordinating a transaction on the source chain with a corresponding action on the destination chain. The original asset may be locked, burned or placed with a liquidity provider; the receiving chain then releases or creates a token representing that value. The process can take minutes or longer, depending on the bridge and both networks.

How does a crypto bridge move tokens?

Most bridges use one of two models: lock and mint, or burn and release. In a lock-and-mint transfer, the source asset stays in a contract or custodian, while the bridge issues a corresponding token on the destination chain. In a burn-and-release transfer, the destination token is destroyed and the original asset is released back on its home chain.

Some bridges instead use liquidity pools. They send destination-chain tokens from a pool and later rebalance the pools across networks. For a breakdown of acrossbridge’s main bridge and swap types, see the separate guide; the key difference is whether a transfer relies on locked assets, issued representations or available liquidity.

• Lock and mint: The original asset remains locked; a corresponding token appears on the destination chain.
• Burn and release: The destination representation is burned before the original asset is released.
• Liquidity swap: A pool supplies tokens on the destination chain, usually in exchange for tokens deposited on the source chain.

Why can a bridge transfer take time or cost more?

A bridge must wait for the source transaction to be confirmed, then verify it before completing the destination action. Some systems rely on validators or other operators to attest that the source transfer happened; others use contracts and proofs. Each network charges its own transaction fee, and the bridge may also charge a service fee or include a price spread.

A transfer can remain pending if the source chain is congested, the bridge has not collected enough confirmations, or destination execution fails. Check the bridge’s status page or transaction record before retrying: submitting again can create a second transfer if the first one is still processing.

What should you check before bridging?

Confirm the destination network, token and receiving address before signing. A token with the same ticker on two chains may be a different contract, and wallets may show a bridged representation rather than the asset’s native version. Make sure you can access the destination network and have its native token for later transaction fees.

For most readers, the better choice is a bridge with a clear transfer status, published fees and a straightforward route back to the original chain. Start with a small amount when using an unfamiliar route, and verify that the received token is usable where you intend to send or trade it. The transfer is complete only after the destination transaction confirms and the token appears in your wallet.