IBC (Inter-Blockchain Communication Protocol)
Protocolo P2P
Comunidad
Detalles
Licencia Apache-2.0
Estado de Desarrollo 🟢 Activo
Propietario No single owner — a "Protocol team" maintains the core spec, with individual ICS standards sometimes maintained by other organizations (Strangelove Ventures, Cosmos Hub team).
Órgano de Gobierno Community-governed spec repository; no single company or foundation controls it, though the Interchain Foundation has historically funded core development.
País N/A
Año de Inicio 2021
Stack Protocol-agnostic spec; primary implementations in Go (ibc-go, for Cosmos SDK chains) and Rust (ibc-rs).
Financiamiento 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).
Última Investigación 23 ago 2026
Protocolo P2P Atributos
Orígenes Cross-chain interoperability for the Cosmos ecosystem's "Internet of Blockchains" vision — enabling sovereign chains to communicate without a central relay or trusted bridge.
Base de Datos N/A
Lenguaje de Consulta N/A (Interchain Queries, ICS-32, provides a query mechanism for cross-chain state reads)
Formatos de Datos Protobuf-encoded packets.
Edición Colaborativa en Vivo N/A
Edición de Texto Enriquecido N/A
Soporte Móvil N/A (infrastructure-layer protocol, not end-user-facing)
Soporte Web N/A directly (wallets/apps built on IBC-enabled chains expose it to end users)
Aplicaciones Nativas N/A
Términos Free, open protocol; relayers may charge fees for their service (market-determined, not protocol-mandated).
Fondos Not centrally tracked (see Funding).
Basado En 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).
Arquitectura P2P Relayer-facilitated packet relay between chains, with light-client verification on each end (no trusted intermediary — relayers are permissionless and can't forge packets).
Red de Superposición 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).
Direccionamiento por Contenido No.
Local-First N/A
Cifrado de Extremo a Extremo (E2EE) N/A (packets are cryptographically verified via light clients, not encrypted in the E2EE sense)
Biblioteca de CRDTs N/A
Tolerancia a Fallos Bizantinos Inherits BFT guarantees from the underlying chains' own consensus (IBC itself doesn't add a new consensus layer).
Firma Depends on the underlying chain's signature scheme; IBC packets are verified via Merkle proofs against the counterparty chain's light client.
Permisos Permissionless — any two IBC-enabled chains can establish a connection without a central authority's approval.
Compatibilidad con la Web Semántica No.
Contrato Inteligente N/A directly, though IBC packets can trigger smart-contract execution (e.g. ICS-20 token transfers, ICA — Interchain Accounts for remote contract calls).
Posición en la Pila del Protocolo Interchain transport/communication layer, sitting above individual chains' consensus layers.
Incorporación de Activos/Valor Via ICS-20 (fungible token transfer standard) — enables cross-chain asset movement, but the protocol itself doesn't define a native asset.
Madurez del Protocolo / Estandarización Mature, formal ICS (Interchain Standards) process with defined standard numbers; in production use connecting 100+ chains as of this writing.