You should read through their White Paper that I linked. They explain all of the technical details of how their system will operate.

Here is an excerpt from their document:

Layer-1 Blockchain Topology Summary

We propose a unique and elegant roundtrip structure for a blockchain architecture which is both groundbreaking and simple. Social net (or any app) → server (e.g. EC2 or a decentralized server, it’ll be up to the app) → API → RevPop layer-1 → pointer → storage → API → server → social net (or any DApp). We’ve devised a method that can combine decentralization, security and speed. This layer-1 is a database enabling users to have control and ownership over their data, with other elements of the infrastructure residing off-chain to enable fast throughput. This, combined with an innovation on the Proof Of Stake consensus mechanism, would allow this layer-1 to service users at scale.

Consensus Mechanism

A protocol based on dPOS “delegated Proof Of Stake” can achieve a robust transactions per second (TPS) rate - using either dPOS itself, or something accretively innovative such as our plan for rdPOS “random delegated Proof Of Stake”. A consensus mechanism with 63 pre-elected nodes, but with 21 randomly selected pre-determined nodes serving at any given time, can mean fast transaction speeds along with security, scalability and elected accountability. Due to the maturation of consensus algorithms, along with ongoing innovation and technological improvements, a modern social network, or any modern application for that matter, should have no problem operating on a blockchain technology foundation that functions as a database.

rdPOS behaves like its predecessor. At the final stage, during the vote counting phase, 21 active witnesses are chosen randomly from the list of TOP 63 candidates. This attracts more nodes to the production of blocks while keeping the number of active producers small, speeding up the blockchain. Test Net available at testnet.revolutionpopuli.com.

Pseudo-random number generation in the blockchain is not an easy task. We’ve implemented a commit-reveal scheme for obtaining a random seed each time 21 new active witnesses are selected. Now, by randomizing the selected block producers, coupled with regular, robust and public elections, the mix of producers is different for every block, and each producer remains accountable. This functionally removes the threat of “centralization” that had been at the heart of the critique of dPOS consensus in the past. It’s important to note that the number of top elected candidates can be calibrated, e.g. if the system proves to be so lightening fast, and updating from 63 TOP to 126 TOP has de minimis (or acceptable) impact on speed, then such a change can always be implemented if the community deems it worthwhile - or the community can even seek to randomize the total number of TOP witnesses per cycle. The system, by the nature of its structure can be self-improving and ever-striving to functionally obviate the “Tri-lema”, to allow speed, security and decentralization to all co-exist in harmony.

In short, this elegant innovation of randomizing block producers, we feel, is a powerful enhancement.