Cross-Chain Transfer

A cross-chain transfer is the movement of a cryptoasset, or of its economic value, from one blockchain to another. Blockchains are separate ledgers that cannot read each other's records directly, so a token held on one chain cannot simply be sent to an address on another. Cross-chain transfers solve this with intermediary mechanisms, most commonly a blockchain bridge, which takes the asset out of circulation on the source chain and makes an equivalent amount available on the destination chain.

Users make cross-chain transfers to reach applications, lower fees or faster networks, for example moving stablecoins from Ethereum to a layer 2 network or to another layer 1 chain. Payment firms and exchanges use them to manage liquidity across chains. The wider field is known as blockchain interoperability.

• Lock and mint. The user's tokens are locked in a smart contract on the source chain, and a bridge issues the same amount of wrapped tokens on the destination chain. Moving back reverses the process: the wrapped tokens are burned and the originals unlocked.
• Burn and mint. Where the token issuer controls the token on several chains, tokens are burned on the source chain and newly minted on the destination chain. Circle's Cross-Chain Transfer Protocol uses this method for USDC, so that the asset on each chain is native rather than wrapped.
• Liquidity networks. The user deposits tokens into a pool on the source chain and receives tokens from a pool on the destination chain, with liquidity providers or market makers balancing the pools. No new tokens are created.
• Swaps and intents. The user expresses a desired outcome, such as receiving a token on another chain, and a solver or market maker fills it using its own inventory, settling with the user afterwards. Atomic swaps achieve a similar result without a trusted party by using hashed time-locked contracts.

The destination chain needs proof that the tokens were really locked or burned on the source chain. Bridges use different approaches. Some rely on a set of validators or a multi-signature group that observes the source chain and signs messages; their security depends on the honesty and key security of that group. Others use light clients or zero-knowledge proofs that verify the source chain's state on the destination chain, which reduces trust assumptions but can be costly. Optimistic designs accept messages unless someone proves fraud during a challenge window. Messaging protocols generalise these methods to carry arbitrary data and cross-chain contract calls, not just tokens.

Bridges have been among the largest targets for hackers because they hold large pools of locked assets. Several incidents have led to losses of hundreds of millions of US dollars each, often through compromised validator keys or flaws in smart contract code. Other risks include:

• Wrapped asset risk. A wrapped token is only as good as the bridge holding the original; if the bridge is drained, the wrapped tokens may lose their backing.
• Finality and reorganisation. If the source chain reorganises after a transfer, the bridge may release assets that were never truly locked.
• User error. Sending to an unsupported chain or address can result in permanent loss.
• Fragmentation. Several versions of the same asset may exist on one chain, issued by different bridges, which confuses users and splits liquidity.

Cross-chain transfers are used by legitimate users, but they are also used to launder stolen funds, a practice sometimes called chain hopping, because moving assets across chains can break the trail followed by investigators. Blockchain analytics firms now trace flows across bridges, and regulators expect virtual asset service providers to consider cross-chain activity in their monitoring and in applying the FATF travel rule. Some bridge operators have frozen or blocked addresses linked to hacks or sanctions, which raises questions about how decentralised they are.

For payment providers that settle in stablecoins, cross-chain transfers allow funds received on one network to be paid out on another preferred by the recipient. Native burn-and-mint protocols are generally favoured for this purpose because they avoid wrapped-asset risk and keep the issuer's redemption promise intact. Providers still need to manage fees on both chains, confirmation times and the operational risk of failed or delayed messages, and they must reconcile balances held on many chains as part of their stablecoin liquidity management.

Developers continue to work on safer and simpler cross-chain designs, including shared security models, proof-based verification and wallets that hide chain selection from users altogether. Standards for messaging and token representation are emerging, but there is no single agreed approach, and users still need to understand which mechanism and which trust assumptions sit behind each transfer they make.