---
title: "Radix vs Polkadot"
path: "/contents/tech/comparisons/radix-vs-polkadot"
version: "1.3.0"
author: "Hydrate"
createdAt: "2026-02-19T05:51:32.304Z"
updatedAt: "2026-07-18T11:08:44.045Z"
---

# Radix vs Polkadot

<Infobox>
| **Radix** | Unlimited shards, native composability |
| **[Polkadot](https://polkadot.com)** | Limited parachain slots, shared security via relay chain |
| **Key Difference** | Infinite sharding vs fixed parachain capacity |
</Infobox>

## Overview

Both Radix and [Polkadot](https://polkadot.com) address scalability through sharding, but with very different architectures:

### Sharding Model

**Polkadot** uses a hub-and-spoke model: parachains (application-specific shards) connect to a relay chain that provides shared security. Parachain slots are limited and auctioned — creating artificial scarcity.

**Radix** uses [Cerberus](/contents/tech/core-protocols/cerberus-consensus-protocol) with effectively unlimited shards. Consensus is braided dynamically per-transaction across relevant shards — no slot auctions, no capacity limits.

### Composability

Polkadot's XCM (Cross-Consensus Messaging) enables cross-parachain communication, but it's asynchronous. Radix provides [atomic composability](/contents/tech/core-concepts/atomic-composability) across all shards — critical for [DeFi](https://en.wikipedia.org/wiki/Decentralized_finance) where partial execution can mean lost funds.

## Scalability in practice (2026)

The braided, effectively-unlimited-shard architecture described above is the design of [Cerberus](/contents/tech/core-protocols/cerberus-consensus-protocol), not the current state of the live network. [Babylon](/contents/tech/releases/radix-mainnet-babylon) mainnet today runs a single, **unsharded** Cerberus instance; multi-shard consensus is being delivered through the [Hyperscale](/contents/tech/research/hyperscale-rs) program (the [eMunie → Tempo → Cerberus → Xi’an](/contents/tech/research/consensus-evolution) lineage). A [January 2026 public test](/contents/tech/research/hyperscale-500k-tps) sustained **500,000+** real cross-shard transactions per second (peaking above 800,000) across 128 shards, as detailed in the [Radix Hyperscale update](https://www.radixdlt.com/blog/hyperscale-update-500k-public-test-done).

Against [Polkadot](https://polkadot.com), the practical difference is capacity model: Polkadot’s throughput is bounded by a fixed number of auctioned parachain slots on its relay chain, whereas Radix’s Hyperscale target is to add shards without slot auctions or capacity caps, preserving [atomic composability](/contents/tech/core-concepts/atomic-composability) across every shard rather than relying on asynchronous cross-parachain messaging (XCM).

## See also

- [Hyperscale: 500K TPS Public Test](/contents/tech/research/hyperscale-500k-tps)
- [Consensus Evolution at Radix](/contents/tech/research/consensus-evolution)
- [Radix vs Cosmos](/contents/tech/comparisons/radix-vs-cosmos)