Cross-Chain

Cross-chain describes any activity, application, or infrastructure that spans more than one blockchain — moving assets from Ethereum to Solana, triggering a contract on one chain from another, or aggregating liquidity across several networks. Because each blockchain is an isolated system that cannot natively read another's state, everything cross-chain depends on connecting infrastructure: bridges that lock-and-mint assets, messaging protocols that relay verified data, and swap systems that coordinate trades across ledgers.

The mechanisms vary in how much trust they require. At one end, atomic swaps use hash time-locked contracts so two parties can trade coins on different chains with no intermediary — either both sides complete or both refund. In the middle, protocols like Cosmos's IBC let chains verify each other's blocks via light clients. At the more trusted end, most popular bridges and messaging networks rely on validator committees or multisigs whose honesty users must assume. For example, a user might bridge USDC from Ethereum to a layer 2 to trade cheaply, with a cross-chain messaging protocol attesting to the deposit on the destination side.

A common misconception is that cross-chain and multi-chain are the same; a multi-chain app deploys separate copies on several chains, while cross-chain means those chains actually communicate. Cross-chain infrastructure is historically where crypto's worst security failures concentrate — the Ronin and Wormhole bridge exploits each lost hundreds of millions of dollars — because a bridge aggregates value behind a single point of failure that is easier to attack than either chain it connects.