whitepaperInteroperability2016
Cosmos: A Network of Distributed Ledgers
Cosmos. Jae Kwon and Ethan Buchman.
The Cosmos paper: independent zones running a BFT consensus, connected by a hub, speaking a packet protocol that later became IBC. Unlike Polkadot's shared-security vision, zones here are sovereign. They choose their own validator sets.
The problem the paper names
Applications forced onto one chain share its governance and its fee market whether they want to or not. Applications on unrelated chains cannot move value without a trusted custodian. Cosmos proposes a standard packet format and a hub so zones can connect without becoming the same chain.
What the design proposes
- Tendermint-style BFT is the default consensus. A zone may be different if it speaks the packet protocol.
- The hub is a zone whose job is routing, not the owner of every application's rules.
- Sovereignty is explicit: a zone's validator set can halt or fork that zone without a relay-chain vote.
How the mechanism is specified
- Light-client proofs are how one zone checks another's header before accepting a packet.
- Peg zones, in the paper, are the intended door to chains that do not speak the protocol natively.
- IBC as shipped has its own specification. Cite that spec for implementation claims, and this paper for the architecture.
What this page does not treat as proven
- Sovereignty means a zone can fail on its own. The hub does not lend it security.
- A peg to an external chain reintroduces the custodian or bridge assumption the paper is trying to narrow.
- The paper is not a map of the current Cosmos token or any particular zone's status.
Why a venture studio still reads it
Use Cosmos when a venture wants several ledgers and is willing to say that they do not share security. Use Polkadot's paper when they are not willing to say that. The distinction is the design choice, not a ranking.
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.