---
title: "Radix Technology"
url: "https://radix.wiki/contents/tech"
updated: 2026-09-03
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
version: "1.0.1"
---

# Radix Technology

| Consensus | [Cerberus](/contents/tech/core-protocols/cerberus-consensus-protocol) |
| --- | --- |
| Execution | [Radix Engine](/contents/tech/core-protocols/radix-engine) |
| Contract language | [Scrypto](/contents/tech/core-protocols/scrypto-programming-language) |
| Model | [Asset-oriented programming](/contents/tech/core-concepts/asset-oriented-programming) |
| Current release | [Babylon](/contents/tech/releases/radix-mainnet-babylon) |
| Open question | Sharded scale, at [Xi’an](/contents/tech/releases/radix-mainnet-xian) |

## Introduction

Radix is a layer-one network built around a claim that sounds modest and is not: that a ledger should understand what an asset is. On nearly every other network an asset is a convention – a balance held in a contract’s storage, obeying whatever rules that contract’s author wrote and whatever bugs they left. On Radix, assets are objects the [Radix Engine](/contents/tech/core-protocols/radix-engine) holds and moves itself, and application code can only ask the engine to move them.

Almost everything else in this section follows from that decision, including the parts that are still unfinished.

## The stack

[Cerberus](/contents/tech/core-protocols/cerberus-consensus-protocol) is the consensus layer, a BFT protocol designed so that transactions touching unrelated state can be agreed in parallel rather than serialized into one chain. Above it the [Radix Engine](/contents/tech/core-protocols/radix-engine) executes transactions against a state model of typed objects, and [Scrypto](/contents/tech/core-protocols/scrypto-programming-language), a dialect of Rust, is how developers write for it.

[Core concepts](/contents/tech/core-concepts) is where the vocabulary lives: [resources](/contents/tech/core-concepts/resources), [buckets, proofs and vaults](/contents/tech/core-concepts/buckets-proofs-and-vaults), [badges](/contents/tech/core-concepts/badges), [components](/contents/tech/core-concepts/components) and [blueprints](/contents/tech/core-concepts/blueprints-and-packages). [Core protocols](/contents/tech/core-protocols) covers the layers themselves, and [atomic composability](/contents/tech/core-concepts/atomic-composability) is the property the whole arrangement exists to preserve: any two applications can be combined inside one transaction that either wholly succeeds or wholly does not.

## The rest of this section

[Releases](/contents/tech/releases) tracks the named mainnets from [Olympia](/contents/tech/releases/radix-mainnet-olympia) through [Babylon](/contents/tech/releases/radix-mainnet-babylon) to Xi’an, and the protocol updates between them. [Research](/contents/tech/research) holds the thirteen years of consensus designs behind the current one, including the abandoned ones. [Comparisons](/contents/tech/comparisons) sets Radix against Ethereum, Solana, Cosmos and Polkadot. [Operations](/contents/tech/operations) covers running against the live network.

## What is settled and what is not

The execution half of the design is live and has been since Babylon in September 2023. [Asset-oriented](/contents/tech/core-concepts/asset-oriented-programming) programming, badges, [manifests](/contents/tech/core-protocols/transaction-manifests) and the wallet are all in production, and the properties they claim can be checked against mainnet today.

The scalability half is not. Cerberus as specified runs unsharded on mainnet, the braided cross-shard consensus in the whitepaper has never shipped, and the sharded design that motivated the project waits on [Xi’an](/contents/tech/releases/radix-mainnet-xian). A reader evaluating Radix should keep those halves apart: one is a shipped system with a track record, the other is a research programme with promising test numbers and no mainnet.