From DPoS to D-DPoS

DPoS, a well-known and creative consensus mechanism, derived from Graphene technology, by making further improvement on PoS, is being accepted by more and more blockchain systems such as EOS. DPoS solves the complex mining process which is the core problem in Bitcoin network since everyone in the network is rewarded or entitled not based on how much work they actually do, but how many “shares” or amount of coins/tokens they actually hold. To use EOS as an example to illustrate how DPoS works, EOS lets the whole network to vote and then rank how many votes a node gets. Any node holding certain amount of EOS is entitled to vote. The first 101 ranking nodes are elected out primarily. Then, out of the 101 candidates, 21 will be elected to become supernodes. The 21 supernodes will be responsible for generating new blocks and process transactions for the network.

DPoS is a fantastic design that improves greatly the issues faced by BTC and ETH system since there’re only 21 nodes generating blocks instead of all nodes in the network. Due to DPoS, TPS in EOS is much faster than ETH and BTC, practically can reach 10 to 100,000 and theoretically even millions of TPS. However, DPoS has its clear problems. First of all, the so-called voting system is not as simple as described here, with just a simple click on a website to anyone you want to vote for. The actual voting process is much more complex and time consuming, requiring voters to have enough professional knowledge. Thus, among the people who have the right to vote, not too many of them actually participate. A common way this is handled is by allowing the exchanges holding peoples coins to vote for them. As a result, the voting outcome might not reflect the voter´s opinions. The other serious problem is bribery. In EOS, the supernodes are rewarded for their work, about 5 % of the total EOS supply. Unfortunately this large amount drive many Supernode representatives to use incentives to have other people vote for them through bribery or other illegal and unethical ways, so called ballot rigging.

D-DPoS Consensus Mechanism; Secure, Decentralized & High TPS

D-DPoS is created by DBXChain to solve the mentioned problems with ballot rigging. DBXChain is mainly a data-based blockchain infrastructure and primarily serves data transaction on it. Just like when you buy something on Amazon, you can rate sellers to reflect how well their service is. By participating in the network through data transactions, the nodes judge whether the data is OK by the quality of the data, network status of the supernodes (Which is called Trinity nodes in DBXChain) and how well the Trinity node fulfill its function. By confirming everything is OK with the data, a node just automatically vote for the Trinity node, otherwise it doesn’t vote. The ranking rationale of nodes is also different from DPoS, such as how many votes one node gets, and the use of a weighted score. Because to survive on the DBXChain, or to participate in it, you have to generate data transaction, you don’t need to spend extra time or energy to vote since you’ve already done so through the transaction. By this way, it really lowers the voting cost and increases the voting rate.

On the other hand, as to bribery, because it is reactive voting procedure in DBXChain where a node get votes by good behavior, if someone wants to cheat, it must misrepresent the historic contributions of the network, which would lead to very costly fines due to misconduct. Once a node has been selected as Trinity node, it will soon be kicked out when it can’t fulfill its duty. If several Trinity nodes cheats, an improved PBFS algorithm would correct the producing block, and triggering an investigation algorithm. If a node votes for another bad quality node to be a Trinity, once disclosed, it will lose its trust among others and lose the possibility to be elected as Trinity in the future. In that way, if someone wants to cheat in DBXChain, it will become very costly and end up only hurting itself, something that is not possible in DPoS.

In addition, DPoS updates the supernodes list every single day, with a fixed schedule. However, in D-DPoS, the list is updating continuously in real-time. Since it’s hard to predict a node’s network status and data validity, the voting procedure is hard to control by any hostile attackers, making it safer than DPoS.

LEARN MORE ABOUT DBX FOUNDATION AT:

Website: http://www.dbx.one/

Twitter: https://twitter.com/DBXFoundation

Facebook: https://www.facebook.com/DBX-Foundation-2034487803539197/

Medium: https://medium.com/@dbxchain/

Github: https://github.com/dbxone

Official Telegram: https://t.me/DBXOfficial

Chinese Telegram https://t.me/DBXChainCN

Official Email: dbx_official@dbx.one