IBC (Inter-Blockchain Communication Protocol)

P2P Protocol

An open protocol for secure, trust-minimized communication between independent blockchains ("interchain") — packet-based message passing with light-client verification, not a trusted bridge/relay. Defined as a formal spec (ICS — Interchain Standards) in the cosmos/ibc repository, with ibc-go and ibc-rs as reference implementations for Cosmos SDK and Rust-based chains respectively. Maintained by a "Protocol team," though individual standards have alternate maintainers (e.g. ICS-32 is maintained by Strangelove Ventures, not the core team) — a genuinely distributed governance model for the spec itself.

Community
Links
Visit Website See this tool in the graph Suggest an edit

Details

License Apache-2.0
Dev Status 🟢 Active
Owner No single owner — a "Protocol team" maintains the core spec, with individual ICS standards sometimes maintained by other organizations (Strangelove Ventures, Cosmos Hub team).
Governing Body Community-governed spec repository; no single company or foundation controls it, though the Interchain Foundation has historically funded core development.
Governing Body - List
  • Cosmos Labs
Country N/A
Start Year 2021
Stack Protocol-agnostic spec; primary implementations in Go (ibc-go, for Cosmos SDK chains) and Rust (ibc-rs).
Funding Historically Interchain Foundation-funded (grants to core maintainers); individual ICS standards may have other funders (e.g. Strangelove Ventures self-funds its own maintained standards).
Funding - List
  • Interchain Foundation
Last Investigated Aug 23, 2026

Topology view

This tool in the centre and the things it is directly related to. Each line names the kind of relationship.

Topology view: IBC (Inter-Blockchain Communication Protocol)This tool in the centre and the things it is directly related to. Each line names the kind of relationship.IBC(Inter-Bloc…ICS-20 (Based on, Hosts)ICS-20Cosmos SDK (Hosts, Built on)Cosmos SDKIXO (Hosts)IXOInterchain Foundation (Funded by)InterchainFoundationCosmos Labs (Stewarded by)Cosmos LabsCosmos Stack (Member of suite)Cosmos Stack
  • ICS-20 (Tool): Based on, Hosts
  • Cosmos SDK (Tool): Hosts, Built on
  • IXO (Tool): Hosts
  • Interchain Foundation (Organization): Funded by
  • Cosmos Labs (Organization): Stewarded by
  • Cosmos Stack (Suite): Member of suite

Open in Graph Explorer

Use Case Domains

Platform Evolution & Sovereignty

P2P Protocol Attributes

Origins Cross-chain interoperability for the Cosmos ecosystem's "Internet of Blockchains" vision — enabling sovereign chains to communicate without a central relay or trusted bridge.
Database N/A
Query Language N/A (Interchain Queries, ICS-32, provides a query mechanism for cross-chain state reads)
Data Formats Protobuf-encoded packets.
Collaborative Live Editing N/A
Rich Text Editing N/A
Mobile Support N/A (infrastructure-layer protocol, not end-user-facing)
Web Support N/A directly (wallets/apps built on IBC-enabled chains expose it to end users)
Native Apps N/A
Terms Free, open protocol; relayers may charge fees for their service (market-determined, not protocol-mandated).
Funding - List
  • Interchain Foundation
Funds Not centrally tracked (see Funding).
Based On Builds on Cosmos SDK's and Tendermint/CometBFT's light-client design; conceptually related to (but distinct from) other cross-chain messaging designs (LayerZero, Wormhole use different trust models).
Governing Body - List
  • Cosmos Labs
P2P Architecture Relayer-facilitated packet relay between chains, with light-client verification on each end (no trusted intermediary — relayers are permissionless and can't forge packets).
Overlay Network N/A — IBC is a communication protocol between chains, not itself a P2P node network (though the relayer network that carries packets is permissionless/open).
Content Addressing No.
Local-First N/A
E2EE N/A (packets are cryptographically verified via light clients, not encrypted in the E2EE sense)
CRDTs Lib N/A
Byzantine Fault Tolerance Inherits BFT guarantees from the underlying chains' own consensus (IBC itself doesn't add a new consensus layer).
Signature Depends on the underlying chain's signature scheme; IBC packets are verified via Merkle proofs against the counterparty chain's light client.
Permissions Permissionless — any two IBC-enabled chains can establish a connection without a central authority's approval.
Semantic Web Compatibility No.
Smart Contract N/A directly, though IBC packets can trigger smart-contract execution (e.g. ICS-20 token transfers, ICA — Interchain Accounts for remote contract calls).
Protocol Stack Position Interchain transport/communication layer, sitting above individual chains' consensus layers.
Asset / Value Embedding Via ICS-20 (fungible token transfer standard) — enables cross-chain asset movement, but the protocol itself doesn't define a native asset.
Protocol Maturity / Standardization Mature, formal ICS (Interchain Standards) process with defined standard numbers; in production use connecting 100+ chains as of this writing.

Relationships

How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.

Based on
Built on
Funded by
  • Interchain Foundation
Member of suite
  • Cosmos Stack
Stewarded by
  • Cosmos Labs
Hosts