RADIX WikiRADIX Wiki

Overview

Radix and Cosmos take fundamentally different approaches to scalability:

Architecture

Cosmos uses sovereign app-chains connected via Inter-Blockchain Communication (IBC). Each chain runs its own consensus and maintains its own state. Cross-chain operations are asynchronous messages — there's no atomic composability between chains.

Radix uses a single sharded ledger with Cerberus braiding consensus across shards. Cross-shard transactions are atomic — they either fully succeed or fully fail, enabling DeFi composability that's impossible in the Cosmos model.

Trade-offs

Cosmos offers more app-chain sovereignty and customization. Radix offers stronger composability guarantees and a unified DeFi ecosystem. For DeFi specifically, Radix's atomic cross-shard model is more suitable — DeFi protocols need to compose with each other in single transactions.

Scalability in practice (2026)

The braided, effectively-unlimited-shard architecture described above is the design of Cerberus, not the current state of the live network. Babylon mainnet today runs a single, unsharded Cerberus instance; multi-shard consensus is being delivered through the Hyperscale program (the eMunie → Tempo → Cerberus → Xi’an lineage). A January 2026 public test sustained 500,000+ real cross-shard transactions per second (peaking above 800,000) across 128 shards, as detailed in the Radix Hyperscale update.

The contrast with Cosmos is therefore about direction as much as design: Cosmos scales horizontally by launching more sovereign app-chains connected over IBC (each a separate trust boundary with asynchronous messaging), while Radix aims to scale a single atomically-composable ledger by sharding consensus underneath it — keeping cross-shard transactions atomic rather than message-passed.

See also