IBC Protocol: The proof matters, not the messenger
Summarize this article with:

The IBC protocol allows independent blockchains to exchange messages without entrusting their validation to the person carrying them. On October 27, 2026 at 9:09 p.m. UTC, a transfer from ATOM to Osmosis provided an example of this. Osmosis only accepted it after verifying proof taken from the state of the Cosmos Hub.

Illustration of a man holding up a certificate decorated with a network symbol and a validation seal, in front of two messengers crossed out with an orange cross.

In brief

  • More than 115 blockchains: according to the protocol website, they have adopted IBC since its first transfer on April 2, 2021.
  • 12 seconds: October 27, 2026 is the time elapsed between sending an ATOM transfer and its receipt verified on Osmosis.
  • 2 minutes: this is the expiration time set for the transfer studied, beyond which the funds could return to the sender.
  • 3 steps: according to the IBC team, version 2 reduces the connection of two channels to this number, compared to ten previously.

IBC protocol: the relayer transports, it does not validate

A transaction confirmed on one blockchain does not exist for another. Each network maintains its own history, with its validators and rules. A smart contract from chain B cannot therefore rely on a simple message from chain A.

The IBC protocol thus separates two functions. First, relayers carry the packages. There IBC documentation describes them as “off-chain processes, open to all” which carry data from one chain to another. Then the receiving chain itself checks what they are bringing.

This verification is based on a Merkle proof. This sequence of fingerprints demonstrates that a piece of data appears in the state of chain A. Chain B compares it to a state root that it already knows. False proof therefore remains false, regardless of who relays it. On the other hand, without a relayer, the packet remains waiting.

What a thin client keeps

To follow chain A, chain B maintains a thin client. According to the Cosmos documentationit only stores three elements for each height it is updated. This is a timestamp, the state root and the fingerprint of the next validators. The client therefore does not replay any transaction from A.

Its settings remain public. On October 27, 2026, the Cosmos Hub client that tracks Osmosis required a new header to carry the signatures of already known validators. These were to represent more than a third of the voting power. The header also had to have two-thirds of its own set of validators. Its confidence period, the maximum duration between two updates, reached 13.96 days. This deadline remains just under the 14 days of unlocking Osmosis tokens. For its part, the Osmosis client who follows the Cosmos Hub retained 20.96 days, for 21 days of unlocking.

This delay has a concrete consequence. Without an update during this period, the client no longer accepts any headers. The torchbearers do not validate anything, but their activity remains essential. Furthermore, a client freezes as soon as someone submits two valid and contradictory headers for the same height.

IBC protocol: a real transfer, step by step

On October 27, 2026 at 9:09:01 p.m. UTC, a Cosmos Hub transaction issued packet #5,022,610. It carried 0.088836 ATOM to Osmosis. Its timeout was 9:11:02 p.m., two minutes later.

On Osmosis, the relayer first updated the Cosmos Hub thin client. It passed it the block header 33 607 730, which follows the sending block. Osmosis was thus able to verify the proof of the package against a recent state root. It all happened in a single transaction, at 9:09:13 p.m., twelve seconds after sending. She updated the client, then recorded receipt of the package, which Osmosis then confirmed.

At each stage, Osmosis therefore controlled proof, not the word of an intermediary. Without on-time delivery, a relayer could have proven to the Cosmos Hub that the package was not received by the deadline. The latter would then have returned the funds to the sender.

IBC v2: fewer steps, multiple trust models

In February 2025, the IBC team presented version 2 of the protocol. Packets flow between a pair of clients, without the connections and channels of the classic version.

IBC v2 is the evolution of IBC: it clearly simplifies the protocol while retaining its expression capacity.

Susannah Evans, then product manager of IBC at Interchain Labs, now Cosmos Labs, announcement of February 20, 2025

This version also links IBC to Ethereum, with other verification modes. On Ethereum, a contract verifies zero-knowledge proofs. The SP1 virtual machine produces them by running a Cosmos Hub thin client. On the Cosmos Hub, an Ethereum light client inversely follows the Ethereum consensus.

THE official repository of IBC v2 However, another tool is planned for chains without thin clients. This attestation client works like a multisignature. Trust then relates to its signatories, and no longer to a consensus. On Ethereum and Solana, a security tip can also restart a frozen client. According to the filing, the contracts themselves do not impose the deadline supposed to govern its decisions.

IBC protocol: what the evidence does not guarantee

An IBC proof is only as good as the consensus of the source chain. According to Cosmos documentation, malicious validators controlling more than two-thirds of the validating power can produce a string with arbitrary state roots. The thin client cannot then detect the fraud. The documentation talks about a “accepted risk of this thin client implementation”.

Furthermore, proof establishes that an application has recorded an instruction. It does not guarantee that this application is flawless. Before judging a connection, ask yourself which client is protecting it. This can be a thin client, a zero-knowledge proof or a multisignature.

On October 27, 2026, the two clients connecting the Cosmos Hub and Osmosis showed no freezing. Their confidence period remained exactly one hour less than the unblocking period of each channel. Our guide to the Cosmos universe presents the chains that the IBC protocol connects.

Maximize your Tremplin.io experience with our ‘Read to Earn’ program! For every article you read, earn points and access exclusive rewards. Sign up now and start earning benefits.

Similar Posts