The coming of Radix DLT heralds good tidings to the world of decentralized ledger technologies (DLT) and decentralized finance projects. A lot of the DLTs out there were not designed with decentralized applications in mind. This has made developers to suffer buildability and scalability issues when they are creating their dApps. With the coming of Radix, the first layer 1 protocol specifically built to serve DeFi, these problems have been solved.
What is The Cerberus?
The Cerberus is an important aspect of the Radix solution, as it acts as the platform's consensus algorithm. This consensus algorithm is built using the “pre-sharding” concept. It is different from the typical method of trying to place sharding to a monolithic ledger. What pre-sharding means is that the ledger is divided into a shard space. This space will host a myriad of shards. The shards will be too numerous to count. They will then be used to represent whatever Radix wants. Cerberus is designed to braid the consensus through the required number of shards.
Cerberus' Core Insights
The Cerberus makes use of three major insights to function.
- It goes from the traditional global ordering that is common and embraces partial ordering. Almost every DLT, out there, makes use of global ordering. What this means is that every transaction has to be put in the same timeline.
In some types of sharding, various globally ordered timelines will be created, while fixed global ordering will exist in every one of them.
Cerberus adds cream to the top by having the presumption that every transaction will show exactly those shards that are important to it. This will occur to every transaction that is done.
- At this stage, it knows what shards should be added to the transaction. The next thing to do is to create a braiding, which is new type of BFT-style consensus.
Usually, BFT-style consensus is able to complete a transaction by making use of two or three phases of signed commitments occurring between nodes.
To function, the braided consensus of Cerberus makes use of the three-phase BFT instance in every shard. It then goes on to braid the commitments to the instances. The commitments used must be offered by the other shards that are related to it.
- The next thing is to create the protocol that allows the three-braid consensus to function in parallel format. Every shard will be allowed to function independently with its resultant BFT instance. The same can be said for the emergent multi-shard instance.
The fact that Cerberus makes use of a 3 phase commit means that it will be more resilient when compared to its counterparts. The fact that Cerberus has the parallelism feature has made it easier to utilize the three-phase commit, without restricting the throughput of the network.
A major contribution of Cerberus is that it takes the usual single-pipe consensus process, then parallelizes it over a myriad of shards or instances. To get this, it synchronizes the shards with 'braids'. The Cereberus is an important aspect of Radix platform that can't be overemphasized.