Radix DLT Cerberus

Here is a simplified explanation of how Cerberus works.

In the blockchain, consensus protocols are required to arrive at an agreement on the ordering of commands such as events, transactions etc. these consensus protocols are stored in one timeline in chronological order. These operation is called global ordering or parallelism.

Why Cerberus?

If global ordering must be eliminated in the application layer, it must be replaced with a suitable alternative. With Radix, an application layer that breaks the functionality of DLT by components can be seen in the design of Radix Engine.



The subject of scalability in Cerberus is an oft-discussed one, with many questions as regards the scalability limitations of Cerberus. This Radix application has no theoretical limitation to how much independent transactions it is able to process. It’s safe to say Cerberus scales linearly.


Cerberus’ safety protocol is guaranteed by its Byzantine Fault-Tolerant. By using multi-phase commits, Cerberus possesses not just safety but liveness. The fprmer guarantees safety while the latter guarantees positive outcomes.

3-phase commit

3-phase commits in Cerberus opens way for a consensus process that are easy to predict and resilient. Cerberus’ design utilizes its parallelism in order to fully use the 3-phase commit while still maintaining overall throughput of the network.


With Cerberus, nodes are permitted to participate with virtually anything from Raspberry Pi to full server down. These node runners will serve as much shard space as possible with whatever bandwidth, storage and processor that is available.

What happens when the network goes down?

Under such circumstance, nodes are known to to rejoin by resynchronizing the transactions that were processed during disconnection. On the other hand, if 1/3 of nodes are disconnected, transactions cannot be processed while nodes remain disconnected from a big chunk of the network.

  • Validator selection
  • Node mapping
  • Sybil protection


The adaptability of Cerberus can be seen in the way it responds when a shard goes rogue. It reemploys the Virtual Quorum Certificate routine in order to address the problem of a rogue shard.

State Machine Replication

Like many other technologies, Cerberus also operates with the State Machine Replication technique for organizing client engagements with server replicas after replicating servers. Typically, State Machine Replication are used to replicate the state of their ledger across their network of nodes.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store