Introduction
The Cerberus whitepaper, first published on arXiv in August 2020, presents a consensus protocol designed to achieve parallelised transaction processing across an effectively unlimited number of shards while preserving atomic composability. The paper was authored by Florian CΓ€sar, Daniel P. Hughes (founder of Radix), Joshua Primero, and Professor Mohammad Sadoghi of the University of California, Davis.
Unlike most blockchain whitepapers that remain unreviewed, Cerberus underwent rigorous academic scrutiny and was accepted into the Journal of Systems Research (JSys) in 2023 after a full peer-review process. This places Radix among a small number of public ledger projects whose core consensus mechanism has been validated to the highest academic standards.
Paper Overview
The paper addresses a fundamental tension in distributed ledger design: how to shard a network for scalability without sacrificing the ability to atomically compose transactions across shards. The authors argue that existing sharded protocols either impose global ordering (limiting throughput) or sacrifice atomicity (breaking composability).
Problem Statement
Traditional blockchains process transactions sequentially on a single chain, creating a throughput bottleneck. Sharding partitions the ledger across independent groups of validators, enabling parallel processing. However, when a transaction touches data on multiple shards, the shards must coordinate β and prior approaches either relied on expensive cross-shard locking mechanisms, required global consensus, or could not guarantee atomicity.
Three Protocol Variants
Cerberus is presented in three variants of increasing robustness:
- Core-Cerberus β operates under strict environmental assumptions with well-behaved clients, requiring no additional coordination beyond single-shard BFT consensus. Each shard independently decides to commit or abort, and the UTXO-based state model prevents double-spending without global ordering.
- Optimistic-Cerberus β avoids extra coordination phases during normal operation but includes recovery mechanisms for Byzantine behaviour, accepting higher costs only when attacks are detected.
- Pessimistic-Cerberus β adds proactive coordination phases that allow operation in fully adversarial environments, trading some latency for consistent safety guarantees regardless of client behaviour.
UC Davis Collaboration
In 2020, Radix partnered with UC Davis' ExpoLab, led by Professor Mohammad Sadoghi, to provide independent academic validation of Cerberus. The ExpoLab team included postdoctoral fellow Jelle Hellings, and PhD candidates Suyash Gupta and Sajjad Rahnama β researchers with deep expertise in Byzantine fault-tolerant systems.
The collaboration focused on four areas:
- Formal mathematical proofs β creating rigorous proofs of safety and liveness for each protocol variant, going beyond the original whitepaper's informal arguments.
- Security analysis β identifying potential attack vectors (equivocation, cross-shard deadlocks, validator collusion) and verifying that the protocol's mitigations hold under adversarial conditions.
- Implementation testing β deploying Cerberus on ExpoLab's ExpoDB platform to benchmark real-world performance, latency, and throughput characteristics.
- Comparative analysis β benchmarking Cerberus against other sharded BFT protocols (AHL, ByShard, Caper) on scalability, liveness, and safety metrics.
The resulting peer-reviewed evaluation, published in JSys, confirmed that Cerberus achieves linear throughput scaling with the number of shards while maintaining atomic cross-shard commitment β a combination no prior protocol had demonstrated under formal analysis.
Key Technical Contributions
The paper makes several contributions to distributed systems research:
- Braided consensus β Cerberus "braids" independent single-shard BFT consensus instances (3-chains) into an emergent multi-shard consensus (a 3-braid). Each shard runs its own HotStuff-derived BFT instance; when a transaction spans multiple shards, their consensus processes are temporarily linked to reach a joint commit-or-abort decision.
- Minimised coordination β cross-shard commitment requires only a single additional consensus step per involved shard, with no global ordering or leader election. Shards that are not involved in a given transaction are unaffected.
- UTXO-based conflict prevention β by adopting a substate (UTXO-like) model, data must be consumed and recreated to be modified, preventing concurrent modification conflicts without cross-shard locks.
- Cluster-send primitive β a communication primitive that prevents equivocation by ensuring a validator cannot send conflicting messages to different shards within the same transaction.
