The Radix History


#1

**Daniel Hughes , founder & CTO of Radix DLT invented the Radix platform and ‘Tempo’ - it’s underlying engine comprised of the consensus algorithm and data architecture.

In 2011, he discovered Bitcoin and was instantly hooked by the underlying elegance of its decentralized protocol. As he dug deep, he quickly realized it’s limitations and proposed various solutions on the Bitcoin Talk Forum, only to be met with criticism. Ultimately, he decided to build his own decentralized ledger that could scale to support mass market decentralized applications with millions of users simultaneously. This obsession with building a truly scalable distributed ledger led him to build and test various suitable consensus algorithms and data architectures like blockchains, block-trees, directed acyclic graphs (DAG) and state channels. Having tested their limits, he found they all had a fundamental inability to scale. So he dedicated his time to developing a new architecture and consensus algorithm. Five years in R&D and after many iterations, he eventually invented ‘Tempo’ - a novel distributed ledger architecture and consensus algorithm for decentralized systems, that is sharded to scale in an efficient, unbounded linear fashion. It uses vector clocks for generating a partial ordering of events in a distributed system to detect and prevent causality violations.

This system is both “asynchronous”, meaning there is no block time, and byzantine fault detective, meaning that it can detect and stop false transactions and double spends within a system that anyone can join.

Tempo does this by preserving the total order of events, allowing for the trustless transfer of value, timestamping and other functionality. It is a semi-structured, shardable architecture that limits state transfer information to only those members of the network that need it. This reduces overhead and increases performance.

It does not require large amounts of computing power (PoW) or large amounts of capital (PoS) to secure it. It is suitable for both public and private deployments, without modification, and requires no special hardware or equipment.Combined with a huge, overlapping shard space, the scalability of Radix is only constrained by the number of Nodes operating within the network.