Cosmos Hands IBC Protocol to Linux Foundation Decentralized Trust

Cosmos has contributed the Inter-Blockchain Communication protocol (IBC) to the Linux Foundation Decentralized Trust (LFDT), placing the cross-chain standard under neutral foundation governance while Cosmos Labs retains a central engineering role.

IBC lets independent ledgers exchange assets and data. According to the technical explanation published by LFDT, relayers carry messages and supporting proofs between chains, and the receiving chain verifies those proofs. Organizations using the protocol keep running their own infrastructure — a design choice that distinguishes IBC from bridge-based models that concentrate custody.

The scale of the network it governs is substantial. A Map of Zones report recorded $45.68 billion in IBC transfers from October 2021 through September 2026. It observed 229 chains sending or receiving IBC traffic during 2025. Those figures cover observable public-network activity only, not private ledgers.

Who is backing the move?

The Cosmos Labs release identifies Google Cloud as a supporter of the contribution. Individuals from Wells Fargo, Injective Labs, OpenZeppelin and Cardano Foundation are also listed alongside it. The roster spans cloud infrastructure, traditional banking and three distinct blockchain ecosystems — a signal that IBC's stewardship is meant to look broader than the Cosmos community alone.

The project's initial committee lists seven maintainers: five from Cosmos Labs, one from Datachain and one from OpenZeppelin. Cosmos Labs remains a primary maintainer and says it will continue committing engineering resources and shaping the roadmap alongside the other maintainers. In practice, Cosmos keeps the keys to the codebase; the foundation holds the frame around it.

What does the governance change for developers?

Under the published governance rules, maintainers hold day-to-day authority and code-merge rights. Specification changes require a public architecture decision proposal. A proposal proceeds if no maintainer objects within five working days; unresolved objections go to a committee vote. New maintainers join through majority committee approval after sustained contributions — a meritocracy with a paper trail.

The release policy is deliberately granular. It provides for component-specific upgrades rather than treating every release as a system-wide change. Breaking changes require a major-version increase, and on-chain contracts ship only after deliberate, reviewed changes rather than on a fixed schedule. That matters for teams building production systems on IBC, since predictable versioning reduces integration risk.

Licensing stays permissive. Cosmos says LFDT will hold the IBC trademark. The contribution guidelines specify Apache 2.0 for code, Community Specification License 1.0 for specifications and CC BY 4.0 for documentation. The code was already public and freely licensed before the handover, so developers retain the ability to use it, fork it and build on it.

What does this change for the market? Not the licenses — those were open before. The change is institutional: a protocol moving $45 billion in cumulative transfers now sits under Linux Foundation governance, with banks and cloud providers named as supporters rather than spectators.

The next milestones to watch are procedural but decisive — the first architecture decision proposals under the new rules and any additions to the maintainer committee beyond the founding seven, which will show whether stewardship genuinely widens beyond Cosmos Labs' engineering bench.