consensus
README
CONTRIBUTING
Introduction
Blockchain Consensus?
Glossary
Categorizing consensus
Chain-based Proof of Work
Chain-based Proof of Stake
Chain-based Proof of Capacity/Space
Chain-based Hybrid models
Chain-based Proof of Burn
Chain-based Trusted computing algorithms
Chain-based PBFT and BFT-based Proof of Stake
Practical Byzantine Fault Tolerance
Federated Byzantine Agreement
Delegated Byzantine Fault Tolerance
Byzantine Fault Tolerance (BFT)
Ouroboros
HoneyBadgerBFT
Modified Federated Byzantine Agreement (mFBA)
Chain-based others
Chain-based DAG
Proof of Devotion
Magi's proof-of-work (mPoW)
Common Attacks
ThresholdRelay
Powered by GitBook
Have an account? Sign in

Delegated Byzantine Fault Tolerance

Last updated 5 months ago
Edit on GitHub

The dBFT is called the Delegated Byzantine Fault Tolerant, a Byzantine fault-tolerant consensus mechanism that enables large-scale participation in consensus through proxy voting. The holder of the NEO token can, by voting, pick the bookkeeper it supports. The selected group of bookkeepers, through BFT algorithm, reach a consensus and generate new blocks. Voting in the NEO network continues in real time, rather than in accordance with a fixed term.

sed in

  • Neo

  • ByteBall only verified nodes are allowed to be Validation nodes (list of requirements). Users choose in transaction set of 12 Validating nodes. Validating nodes(Witnesses) receive transaction fees. Whitepaper​

Read more

Previous
Federated Byzantine Agreement
Next
Byzantine Fault Tolerance (BFT)