How do cross-chain bridges move crypto? Follow the message
How do cross-chain bridges move crypto between blockchains? They verify a source-chain transfer, then authorize tokens to be minted or released on the destination.
The Chain Today Desk5 min read

Cross-chain bridges verify activity on one blockchain and authorize a corresponding asset to be created or released on another. Suibridge is a fitting example: its lock-and-mint route locks supported Ethereum assets and mints representations on Sui. Each blockchain maintains its own ledger, so a bridge coordinates separate records rather than moving a coin between them.
A bridge turns a verified transfer into a destination transaction
A bridge transfer starts with an instruction on the source chain: deposit, lock, or burn a supported asset. A source contract records that action. The bridge then waits for the required confirmation or finality, so the source event is stable enough under that bridge’s rules to use as evidence.
Relayers carry the event or its proof to the destination. The destination bridge contract checks the message against its verification rules, then authorizes the matching action. The result could be newly minted tokens, a release of tokens held in reserve, or a payout from destination-chain liquidity.
For ETH sent through the lock-and-mint route, the steps are concrete: a user deposits ETH into the Ethereum-side bridge contract; relayers report the deposit; the Sui-side verifier checks the message; and the destination contract mints the corresponding representation to the user’s Sui address. The user receives that representation on Sui, while the original ETH remains locked on Ethereum until the bridge’s release rules allow it to move.
A message identifier is the transfer’s unique reference across those steps. It can bind the source chain and event to a particular destination action. The destination records that identifier as executed, so a relayer submitting the same message again cannot trigger another mint or release. Without that replay protection, one valid deposit could be presented repeatedly as if each submission were a new transfer.
Think of the identifier as a ticket that can be used once: the message proves which transfer is being claimed, and the destination marks the ticket spent. The exact identifier format and verification method vary by bridge, but the goal is the same: match one authorized source event to one destination execution.
The settlement model changes what arrives
Bridge designs differ in where the destination asset comes from and what backs it.
- Lock-and-mint: The source asset is locked, and a representation is minted on the destination. The holder depends on the bridge’s ability to release the locked asset under its rules.
- Burn-and-mint: The source representation is burned, and a corresponding asset is minted on the destination. This suits assets designed to circulate across chains, with the bridge coordinating supply.
- Liquidity-funded payout: A liquidity provider pays the destination asset from funds already there, while the source-side transfer settles separately. The recipient gets a payout without waiting for a new destination mint, but the route depends on available liquidity and its fees.
The visible difference is the asset received: a representation backed by a lock, a newly minted counterpart, or an asset paid from a liquidity pool. Confusing a representation with the original chain’s asset can lead to sending it to a wallet or exchange deposit route that does not support that token or network.
Costs combine source-chain gas, destination-chain gas, and any route or liquidity charge. Timing depends on source finality, relayer delivery, destination verification, and available liquidity. Security depends on the contracts, message verification method, and who has authority over verifiers or upgrades. Relayers may carry messages, but the destination’s verification rules determine whether those messages can authorize execution.
In everyday use, bridges let users move assets to a chain where they want to trade, use an application, or make a payment. Before choosing a route, identify the destination asset and network, how the bridge settles, what it charges, and which contracts or verifiers must behave correctly.
Related questions
Can I bridge directly to an exchange?
A bridge transfer can go directly to an exchange only when the exchange provides a deposit route for the exact destination network and asset. Confirm both details before sending; a token with a familiar ticker may still be a different representation.
Can a smart contract receive bridged tokens?
A smart contract can receive bridged tokens when the destination token and route support that handling. Running the receiving application’s logic requires compatible destination-side execution, so a transfer to a contract address does not by itself guarantee that the application action will run.
Questions to check before bridging
How do I inspect a bridge audit?
Read the audit’s scope, date, contracts reviewed, and findings, then check whether fixes were verified and whether the live contracts match the reviewed version. An audit describes a review of specific code and conditions.
Can bridging create taxable events?
Bridging can have tax consequences that depend on the assets, transaction structure, and local rules. Keep the source and destination transaction records and ask a qualified tax adviser about your jurisdiction.
How do light-client bridges verify transactions?
A light-client bridge checks source-chain data against a compact representation of that chain’s consensus, rather than relying only on a separate verifier group’s attestation. Its security depends on the client implementation and the assumptions behind the consensus proof.
Who can upgrade bridge contracts?
Upgrade authority depends on the bridge’s contract controls: it may rest with an administrator, a multisignature group, or a governance process. Review the deployed contracts and their documented permissions to see who can change the rules.