Blockchain interoperability

Blockchain interoperability is the ability of separate blockchains to pass tokens, messages or other data to one another, which they cannot do on their own because each network keeps its own ledger and rules. Protocols such as IBC in the Cosmos ecosystem and Chainlink's CCIP provide it, along with token bridges, and they differ mainly in whom the receiving chain has to trust that a message really came from the other side.

How many links one chain keeps

How many other chains can one blockchain talk to? The Cosmos Hub, chain ID cosmoshub-4, gave its own answer through a public node at block 33,840,589, at 07:02 UTC on November 12, 2026.

The node listed 1,943 IBC channels running over 1,316 connections, backed by 1,522 light clients. Many of the links were never finished.

Token-transfer channels on the Cosmos Hub Count
Open 586
Stuck partway through opening (TRYOPEN) 110
Only initiated (INIT) 35
Closed 1
Total 732

The other 1,211 channels served other uses, 1,129 of them on ports for interchain accounts, the ICS 27 standard. A channel’s presence on the list says nothing about whether tokens can travel over it today.

Who the receiving chain trusts

Blockchain interoperability starts from a limit, since chains cannot read each other’s ledgers. As ethereum.org’s developer page on bridges puts it, they exist “in siloed environments,” and every interoperability design is an answer to the question of who vouches for a message arriving from outside.

IBC’s answer is the other chain itself. Its documentation describes connections that are “peer-to-peer,” run over self-hosted infrastructure “without a third-party intermediary,” with no in-protocol fees or token.

Chainlink’s Cross-Chain Interoperability Protocol (CCIP) relies on a committee. Its architecture page says each message is proven on the source chain and delivered on the destination by a default network of 16 independent node operators on every lane, its word for a route between two chains, with optional extra verifiers.

The costliest interoperability problems so far have come from small signer groups. Game developer Sky Mavis said in an April 6, 2022 statement that attackers compromised validator nodes of its Ronin bridge on March 23 that year and drained 173,600 ETH and 25.5 million USDC, naming “the small validator set” as the root cause. Further thefts are listed under cross-chain bridge.

Where you see it

On IBC chains the route a coin took becomes part of its name. The token transfer standard ICS 20 writes a received denomination in the form port, channel and original denomination, adding a hop each time the coin moves on and removing one when it goes back the way it came.

The mistake: one coin, two routes

The same coin sent over two different channels does not arrive as the same token. Under ICS 20 each route produces its own denomination on the receiving chain, even though both trace back to one original asset.

Before moving funds between chains, check that the app or exchange at the other end lists the exact denomination or token contract you will hold on arrival, and that the channel or route you use is open.