CoinYQ Dossier

ATOM secures one Hub inside a universe designed to have no single center

Cosmos began with a Hub at the center of a diagram. IBC eventually made the deeper promise possible: sovereign chains could connect without surrendering their own validators. That success narrowed ATOM’s honest domain to Cosmos Hub, its governance, and the consumer chains that explicitly borrow its security.

The founding diagram was a hub, but the principle was sovereignty

The original whitepaper by Jae Kwon and Ethan Buchman described independent zones connected through the first chain, Cosmos Hub. ATOM would bond its validator set, and the Hub would coordinate a multi-asset ledger. The paper also said the Hub was not the center of the universe—a tension that later architecture resolved in favor of many possible hubs and direct connections.

Cosmos Hub became a real sovereign proof-of-stake chain running Gaia. Yet “Cosmos” also came to mean a development stack and an ecosystem of chains. A chain can use Cosmos SDK, CometBFT, or IBC without giving ATOM holders control over its treasury, upgrades, or validators.

Stargate turned interoperability into verified messages

The February 18, 2021 Stargate upgrade installed IBC capability on Cosmos Hub. Asset transfers under ICS20 were enabled separately through proposal 41, whose vote ended with approval on March 29, 2021. In the current protocol, chains maintain light clients of counterparties, relayers submit packets with proofs, and the receiving chain verifies those proofs before changing state. Relayers matter for delivery and liveness, but they do not receive a blanket right to invent valid packets.

This structure breaks the popular shortcut that every IBC route is secured by ATOM. Security follows each chain and its light-client assumptions. Cosmos Hub may be one endpoint or routing venue, but the protocol does not require every transfer to cross the Hub.

ATOM coordinates the Hub validator set

Current parameters admit the top 180 validators by bonded stake. Delegators keep custody while assigning voting power, share rewards, and share slashing exposure; unbonding currently takes 21 days. A validator’s governance vote counts for nonvoting delegators, while a delegator’s own vote overrides it.

Control is divided rather than ownerless. Informal Systems is named as Gaia’s current stewarding development team, but code merged into a repository does not upgrade the live chain by itself. Validators operate binaries and coordinate upgrades backed by governance. The ICF and its Cosmos Labs subsidiary fund and maintain broader stack components, without unilateral authority over all validators or sovereign chains.

Shared security is an opted-in extension, not an ecosystem-wide fact

Proposal 187 passed in March 2023 and approved the v9-Lambda upgrade containing Replicated Security provider code. It allowed the Hub validator set to validate approved consumer chains and receive agreed rewards. A consumer chain still needs its own governance path, and the proposal itself required enough validator power to run the consumer binary before launch.

The distinction changes the investment story. ATOM security can extend beyond the Hub, but only to identified consumer chains under explicit arrangements. Other IBC chains retain their own validator economics and failure modes; their use of Cosmos software does not automatically produce ATOM demand or Hub control.

ATOM 2.0 was a rejected fork in the road

Proposal 82 tried to redefine the Hub around an Interchain Scheduler, Interchain Allocator, new councils, and a 36-month issuance transition. Voting ended on November 14, 2022 with the proposal rejected. Those mechanisms remain evidence of a contested direction, not a list of features that holders received.

Later governance chose a narrower monetary change. Proposal 848 passed in November 2023 and reduced maximum inflation from 20% to 10%. At this review the mint parameters set a 7% floor, 10% ceiling, and 67% bonded target; the live inflation query returned 10%. Supply was 528,834,989.434937 ATOM and had no fixed maximum, so a dated number is a snapshot rather than a cap.

How the project changed

  1. 2016
    The hub-and-zones thesis is written

    Kwon and Buchman describe independent chains, a first Cosmos Hub, Tendermint consensus, and an early Hub-centered IBC design.

  2. 2021-02-18
    Stargate installs IBC capability

    The upgrade provides IBC software capability; it is distinct from the later proposal 41 enabling ICS20 asset transfers.

  3. 2021-03-29
    Proposal 41 approves IBC asset transfers

    The passed parameter-change proposal enables sending and receiving ICS20 assets. Its voting period ended on this date.

  4. 2022-11-14
    ATOM 2.0 is rejected

    Proposal 82 fails, leaving its Scheduler, Allocator, councils, and issuance transition outside the adopted Hub design.

  5. 2023-03-07
    v9-Lambda wins approval

    Proposal 187 passes, approving provider-side Replicated Security code while preserving separate consumer-chain onboarding.

  6. 2023-11-25
    Governance lowers the inflation ceiling

    Proposal 848 passes and cuts the maximum inflation parameter from 20% to 10%.

Evidence and primary sources

Last evidence review: 2026-09-04

What is Cosmos Hub?

Cosmos Hub is the first public chain built from the Cosmos stack, currently running the Gaia application. ATOM is its staking, fee, and governance asset. The wider Cosmos ecosystem includes many independently governed chains, so using Cosmos SDK or IBC does not make a chain subject to ATOM holders.

What problem does Cosmos Hub solve?

The project began with a hub-and-zones vision for moving assets among independent ledgers. The hard governance question became narrower: if chains keep their own validator sets and rules, what durable job belongs to the original Hub and its token?

How does Cosmos Hub work?

ATOM holders can delegate to one of the 180 active validators, share rewards and slashing exposure, and vote on Hub proposals. IBC relayers submit packets and proofs that onchain light clients verify. Replicated Security can extend the Hub validator set to specifically onboarded consumer chains, but it is not the security model of every IBC chain.

Key facts

  • Cosmos Hub is a sovereign chain; the Cosmos ecosystem, Cosmos SDK, CometBFT, and IBC are broader than the Hub.
  • The February 18, 2021 Stargate upgrade installed IBC capability on Cosmos Hub. Asset transfers under ICS20 were enabled separately through proposal 41, whose vote ended with approval on March 29, 2021.
  • IBC relayers carry data and proofs, while receiving-chain light clients verify counterparty state; ATOM is not universal collateral for IBC.
  • Current staking parameters specify 180 active validators and a 21-day unbonding period.
  • Delegators share validator slashing risk; if they do not vote, the validator vote is inherited, and a direct delegator vote overrides it.
  • Proposal 82, ATOM 2.0, was rejected in November 2022; its Scheduler, Allocator, councils, and issuance redesign are not current Hub features merely because they appeared in the proposal.
  • Proposal 187 approved Replicated Security provider code in March 2023, but consumer chains require separate onboarding and validator operation.
  • At review, supply was 528,834,989.434937 ATOM, there was no fixed maximum, and the dynamic inflation parameters were 7% to 10% with the live rate at 10%.

Official links

Categories

Related coins

Frequently asked questions

Does ATOM secure every chain called Cosmos?

No. ATOM secures Cosmos Hub. Sovereign SDK or IBC chains normally have their own validators. A consumer chain shares Hub security only through the distinct Replicated Security onboarding process.

Must an IBC transfer pass through Cosmos Hub?

No. The early whitepaper described a Hub-centered route, but current IBC supports direct connections and channels between compatible sovereign chains. Relayers submit proofs; the receiving light client checks them.

What does staking ATOM do?

Delegation adds voting power to a Hub validator and can earn staking rewards. The delegator also bears slashing and a current 21-day unbonding delay. Delegation does not transfer custody of the tokens.

Who controls Cosmos Hub upgrades?

Developers propose and maintain Gaia code, validators decide what binary to run, and staked voting power approves coordinated onchain upgrades. The ICF and Cosmos Labs fund or maintain parts of the wider stack but do not unilaterally command every Hub validator.

Did ATOM 2.0 take effect?

No. Proposal 82 was rejected on November 14, 2022. Its proposed Scheduler, Allocator, governance councils, and 36-month issuance transition must be treated as an unadopted design.

Is ATOM capped?

No fixed maximum appears in the current minting model. On September 4, 2026 the queried supply was 528,834,989.434937 ATOM; dynamic inflation parameters were 7% minimum and 10% maximum, and the live query returned 10%.

What power does a delegator retain?

A delegator may redelegate, unbond, and cast a proposal vote that overrides the validator vote for that stake. Inactivity leaves the validator vote inherited, so practical influence depends on participation.

External trackers

Choose a tracking site for Cosmos Hub: