Interoperability: how chains talk to each other, and who vouches for the message
Blockchains can't read each other. To pass a message or a token between two chains, something has to carry the message and something has to vouch that it's true: a light client that checks the other chain itself, a committee that signs for it, or a scheme that waits for objections.
Grandma Rosa's sister lives in the next village. She says she has paid Rosa ten coins, written in her own village's notebook. Rosa would like to see those ten coins in hers.
But Rosa's villagers can't read the other notebook. They have never been there. Then a friendly stranger turns up at the gate: he has just come from the next village, he saw the line with his own eyes, and if Rosa will just write it in straight away, he's in a bit of a hurry.
Every connection between two blockchains has this problem. The chains can't see each other. Someone carries the message, and someone has to vouch that it's true. Interoperability is the art of choosing who that is.
What it is
Interoperability means two separate blockchains can pass messages to each other: "I locked these tokens", "this vote passed", "please run this function". Moving tokens across, the job of a bridge, is just one kind of message.
The carrying is the easy part. Anyone can relay data from one chain to another. The hard part is the proof: how does chain B know that chain A really said it? ethereum.org sorts the answers into trusted bridges, which "are externally verified", and trustless ones, which "do not add new trust assumptions (in addition to the blockchains)" (ethereum.org).
How it works: three ways to vouch
1. Check it yourself: light clients. Rosa's village keeps a tiny copy of the other village's notebook: not every line, only the header of each page and the keepers' signatures. Then the messenger must bring the line plus proof that it sits on a signed page.
That is how IBC works between Cosmos chains. Its Tendermint client is "a client (verification algorithm) for a blockchain using Tendermint consensus" (ICS-007): each chain tracks the other's validator signatures and checks proofs against them. "Cosmos explained" covers it in use. The cost: each chain needs a light client for each chain it talks to, and ethereum.org notes that light client designs can limit how many chains connect.
2. Trust a panel: committees. The village appoints a panel of witnesses who watch the other notebook and sign when they see a line. A message counts once enough of them sign.
Wormhole is one example. Its docs say it "relies on a set of 19 distributed nodes called Guardians", and that "a quorum of 13 signatures is required to produce a valid VAA", its signed message (Wormhole docs, read on 19 November 2026). Do the sum:
- To forge a message: an attacker needs 13 of 19 keys, about 68%.
- To block a forgery: 7 honest guardians are enough, because the other 12 can't reach 13 on their own.
- To stop the whole system: 7 guardians going offline, for the same reason, since 19 minus 7 leaves 12.
That is a multisig with extra steps. Strong if the 19 really are independent, weak if one company runs several.
3. Trust a network of oracles, or wait for objections. Some systems use an oracle network to read one chain and report to the other; Chainlink's CCIP, described in "Chainlink explained", is one. Others are optimistic: a message is accepted unless someone objects within a waiting period, the same idea as the optimistic rollups in "Arbitrum and Optimism explained". ethereum.org notes the trade-off: bridges that wait for fraud proofs can be slower.
Why it matters
- Who gains. Users and apps, who can use tokens and services spread over many chains without starting from scratch on each.
- Who pays. Whoever trusted the wrong messenger. With a committee, ethereum.org warns, users must rely "on the assumption that validators will not collude to steal user funds".
- Where the risk sits. In the verifier and in the code. ethereum.org: "all it takes is one flaw in a smart contract for assets to be exposed to hacks". "Why bridges get hacked" goes through the cases.
- Why light clients aren't everywhere. Checking another chain's signatures on chain costs computing work. ethereum.org notes that Ethereum's own light clients rely on a smaller "sync committee" of validators (ethereum.org). Cheap verification is an open problem.
Where people get it wrong
- "Interoperability is the same as a bridge." A bridge moves tokens. Interoperability covers any message, from a token transfer to a governance vote.
- "Cross-chain means as safe as both chains." Only with a light client or proof-based design. With a committee, it's as safe as the committee.
- "Thirteen of nineteen is decentralised." It depends on who holds the nineteen keys. Count the independent organisations, not the keys.
- "The relayer is the one I trust." The relayer only carries the message. Trust sits with whatever checks it at the other end.
Ask who signs the note
Before you move money between chains, find one paragraph in the system's documentation: who verifies messages, how many of them there are, and how many must agree. If the answer is a light client, the other chain vouches. If it's a committee, the committee does.
If you can't find the paragraph at all, you're Rosa at the gate. The stranger is friendly, in a hurry, and swears he saw the line.
Frequently asked questions
What is blockchain interoperability?
Interoperability is the ability of separate blockchains to pass messages to each other, such as "these tokens were locked" or "this vote passed". Blockchains can't read each other directly, so every interoperability system needs a way to carry messages and a way to prove they are genuine.
How do blockchains communicate with each other?
A message is carried from one chain to the other and then verified. The main ways to verify it are a light client that checks the source chain's signatures, a committee of signers that vouches for it, an oracle network, or an optimistic scheme that accepts it unless someone objects in time.
What is a light client bridge?
It is a connection in which each chain keeps a compact record of the other chain's block headers and validator signatures, and checks incoming messages against them. IBC, used between Cosmos chains, works this way. It avoids trusting an outside group but costs more to run and to connect to new chains.
Are cross-chain messaging systems safe?
They are only as safe as whoever verifies the messages, plus the code. A committee system can be broken if enough of its signers collude or are hacked, and any system can fail through a smart contract bug. Check who signs, how many must agree, and who controls those keys.
Is interoperability the same as a bridge?
No. A bridge is one use of interoperability: moving tokens by locking them on one chain and issuing them on another. Interoperability also covers messages that carry no tokens, such as calling a function or passing a vote result.

