Every blockchain is, in a sense, an island. A network like Bitcoin has no built-in way to read what is happening on Ethereum, and vice versa. Each chain keeps its own ledger, runs its own consensus rules, and has no native concept of assets that exist somewhere else. So when someone says they "sent a token from one chain to another," something more complicated is happening underneath. That something is called cross-chain bridging.
The first thing to understand is that tokens almost never actually travel. A token is just a balance recorded in a smart contract or ledger on a particular chain. There is no technical mechanism to pick that record up and place it on a different chain's ledger. Instead, a bridge coordinates two separate actions on two separate chains: something is locked, burned, or otherwise immobilized on the source chain, and a corresponding amount is released or created on the destination chain. The user experiences it as a transfer. The chains experience it as two unrelated transactions that a third party is asserting belong together.
The most common design is lock-and-mint. You deposit an asset into a smart contract or custodial address on the source chain, where it sits frozen. A set of validators, oracles, or a light client then observes that deposit and authorizes the minting of a new token on the destination chain. That new token is a representation, often called a wrapped asset. It derives its value entirely from the promise that the original is still locked up and can be redeemed. To go back, you burn the wrapped token, and the bridge unlocks the original. If the locked reserves are ever lost or stolen, the wrapped version becomes a claim on nothing.
A second design is burn-and-mint, used when a token issuer controls the asset on multiple chains. Instead of locking collateral, the bridge destroys tokens on the source chain and mints an equal amount on the destination chain, keeping the total supply across all chains constant. There is no wrapped derivative here — the token on each chain is equally canonical. This avoids the fragmentation that happens when several different bridges each issue their own wrapped version of the same underlying asset.
A third approach skips issuance entirely and uses liquidity pools. The bridge maintains reserves of the same asset on both chains. You deposit into the pool on one side, and the bridge pays you out from the pool on the other side, rebalancing over time. Because you receive an asset that already existed on the destination chain rather than a newly minted representation, these transfers can feel more like a swap. The tradeoff is that transfer size is limited by available liquidity, and pricing can shift when one side runs low.
The hard problem in all of this is verification. How does the destination chain know the source-chain event really happened? Solutions fall on a spectrum. At one end are trusted bridges, where a company or a fixed set of signers attests to events; this is efficient but concentrates risk in whoever holds the keys. In the middle are bridges secured by a bonded validator set with economic penalties for lying. At the other end are trust-minimized bridges that run a light client of one chain inside a smart contract on the other, cryptographically verifying block headers and proofs. Light clients require the least trust but are computationally expensive and must be built for each pair of chains.
This verification layer is why bridges have historically been a favorite target for attackers. Large sums sit in one place, and a flaw in signature checking, proof validation, or key management can allow someone to mint destination tokens without ever depositing anything. The underlying chains can be functioning perfectly while the bridge between them fails.
Practically, a few habits reduce friction. Confirm which chain and which token standard you are sending to, since an address that looks identical across networks may not be usable on both. Understand whether you will receive a canonical asset or a wrapped one, because wrapped versions from different bridges are not interchangeable. Expect fees on both chains and a delay tied to how many confirmations the bridge requires. And recognize that bridging adds a layer of smart contract and trust risk on top of whatever risk the assets already carry.
This article is for general education only — not financial advice, and nothing here is a recommendation to buy, sell, or hold any asset. Cryptocurrency carries real risk of loss; always do your own research before making a financial decision.
