Protocol Wars & Forks4 min read

Cosmos IBC: When Independent Ledgers Began to Talk

The Cosmos Hub completed Stargate in February 2021 and enabled IBC transfers in March. The gap reveals what connecting blockchains actually requires: clients, relayers and rules for representing another chain’s assets.

Cosmos IBC: When Independent Ledgers Began to Talk

3-Minute Fast Briefing

  • The ParadoxThe Cosmos Hub completed Stargate on February 18, 2021. Proposal 41 enabled IBC token transfers on March 29; these were separate milestones.
  • The Turning PointIn the classic IBC design, clients verify remote-chain state and relayers carry the data. The courier does not acquire the authority to declare a transfer valid.
  • The LegacyICS-20 represents transferred assets with escrow and vouchers. Connected chains keep their own consensus, and their security assumptions still matter.

Chronological Timeline

February 18, 2021Stargate reaches the Hub

The Cosmos Hub restarts as cosmoshub-4 with IBC support included in the upgrade.

March 29, 2021Token transfers are enabled

Proposal 41 activates IBC transfers on the Cosmos Hub; the ecosystem’s March report also records transfers with IRIS Hub.

An Upgrade, Then Another Decision

On February 18, 2021, the Cosmos Hub stopped its old chain, exported its state and restarted as cosmoshub-4. The Stargate upgrade included support for Inter-Blockchain Communication, or IBC. Yet a second date belongs beside that launch: March 29, when governance proposal 41 enabled IBC token transfers on the Hub. Installing the ability to communicate and opening the transfer function were distinct steps.[1][2]

The project’s March report, published in April, recorded the Hub and IRIS Hub enabling transfers and exchanging tokens. The story is easy to compress into a single launch celebration. Keeping the steps separate reveals the more interesting achievement: independent networks had gained a way to act on one another’s records without combining their ledgers.[1][2]

A Ledger Cannot Take a Messenger’s Word

Inside one blockchain, nodes follow a shared set of rules for accepting records. Another blockchain has its own history and consensus. A message saying that funds were locked somewhere else cannot become authoritative simply because a server delivers it. The receiving chain needs a way to check the remote record against a state it recognizes.[3]

Classic IBC addresses this with a client: verification logic paired with an initially trusted view of the other chain. The client checks updates to that view, which can then support verification of proofs about remote state. It need not rerun every transaction on the other chain. This saves work, but it also makes the client’s rules and starting assumptions part of the security model.[3]

The Courier Has Work to Do

A protocol still needs transport. A transaction on one chain does not itself reach across the internet and execute on another. Relayers watch chain state, assemble the required messages and submit transactions to the other side. They also carry acknowledgements and the information needed to process timeouts. These are ordinary off-chain processes doing essential delivery work.[4]

The division of authority is deliberate. Relayers may carry the evidence, but verification occurs on-chain. Under the protocol’s assumptions, an untrusted courier should not be able to make a fabricated packet valid. Availability is a different question: progress requires functioning chains and at least one correct, active relayer for the relevant connection. Verifiable messages still need someone to deliver them.[3][4]

What Actually Crosses the Gap

Token transfer adds accounting rules to this communication machinery. ICS-20 specifies the fungible-token application. In a simple transfer of a native asset from chain A to chain B, the sending side escrows the asset and the receiving side mints a corresponding voucher. The original units have not jumped out of one database and materialized in another; two ledgers record linked operations.[5]

For a return through the same path, the voucher is burned and the escrowed asset is released. The denomination retains information about the channel path, so the route is part of what identifies the representation. This is why an asset’s familiar ticker alone is an incomplete description of what a user holds on a different chain. The provenance of the balance matters.[5]

Connected Does Not Mean Identical

A failed transfer also needs an explicit outcome. ICS-20 provides refunds when an error acknowledgement or a valid timeout is processed. A clock reaching a deadline is not, by itself, a refund transaction: the appropriate information must still reach the chain and be handled. The relayer specification makes this less visible work part of the protocol’s operation.[4][5]

IBC therefore connects systems while preserving their differences. Its client specification still requires assumptions about the remote chain’s consensus, and ICS-20 warns that users sending assets to a faulty chain can be at risk. The 2021 opening was meaningful because it gave independent ledgers a common way to verify and use messages. It did not make every connected ledger equally trustworthy.[3][5]

Connected Lore & Universe

Connected Stories in this Universe

Explore the chain reaction of historical breakthroughs, blunders, and legends.

Sources & References

  1. [1]Source 1: Stargate mainnet upgrade completion, February 2021Cosmos Hub Forum · 2021-02-18Accessed 2026-09-14
  2. [2]Source 2: Cosmos March 2021 report: proposal 41 and IRIS Hub transfersCosmos Hub Forum · 2021-04-07Accessed 2026-09-14
  3. [3]Source 3: ICS-02: client semantics and consensus assumptionsInterchain StandardsAccessed 2026-09-14
  4. [4]Source 4: ICS-18: relayer algorithms, acknowledgements and timeoutsInterchain StandardsAccessed 2026-09-14
  5. [5]Source 5: ICS-20: fungible token transfer, escrow and vouchersInterchain StandardsAccessed 2026-09-14
← Back to all storiesExplore all coins →