dops introduction

Content

The most important thing in the blockchain is the consensus algorithm. Bitcoin uses POW (Proof of Work), Ethereum uses POS (Proof of Stake), and EOS uses BFT-DPOS.

What is BFT-DPOS? That is, the Byzantine fault-tolerant appointment proof of equity.

To understand the operating mechanism of BFT-DPOS, you must first understand what DPOS is.

Because POW greatly consumes algorithm resources in Bitcoin's consensus algorithm. And there will be a problem of algorithm concentration, so in 2014 Dan Larimer proposed a more efficient and lighter consensus mechanism than POW, namely DPOS. On the one hand, the consensus mechanism can miniaturize the network cost, and on the other hand, each shareholder has a certain voting right in reply.

These super nodes can: provide relevant computing resources and network resources to ensure the normal operation of the nodes; when it is the turn of a super node to have the right to produce blocks, the super nodes collect all the transactions in the period and package them into blocks after verification Broadcast to other super nodes, and other nodes will add the block to their own database after verification. This consensus mechanism uses a random witness block generation sequence, the block generation speed is 3 seconds, and the transaction takes 45 seconds to be irreversible. Why does it take 45 seconds? Because under DPoS, the witness produces a new block, which means that he has confirmed the entire previous blockchain, indicating that the witness recognizes the entire current chain. In order for a transaction to reach an irreversible state, more than two-thirds of the witnesses need to confirm. In EOS, there are 14 witnesses. The DPoS consensus algorithm also has strong anti-forking ability, because the rate at which a block is added to a blockchain forked is related to the proportion of super nodes that have the consensus. When a super node manages to produce blocks on two forks at the same time, EOS holders will delete the super node in the next round of voting, and the EOS community will penalize the relevant malicious nodes. Therefore, in general, it is difficult for EOS using DPoS to undergo forks.