consensus
consensus
README
Blockchain Consensus Encyclopedia Infographic
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
leaderless BFT dual ledger architecture
Albatross
asynchronous BFT protocol
BFTree
Byzantine Fault Tolerance (BFT)
Delegated Byzantine Fault Tolerance
Federated Byzantine Agreement
HotStuff
LibraBFT
Modified Federated Byzantine Agreement (mFBA)
Ouroboros
Practical Byzantine Fault Tolerance
Chain-based others
Chain-based DAG
Magi's proof-of-work (mPoW)
Common Attacks
Performance indicators
ThresholdRelay
Holochain
Powered by GitBook

Delegated Byzantine Fault Tolerance

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
Byzantine Fault Tolerance (BFT)
Next
Federated Byzantine Agreement
Last updated 2 years ago
Edit on GitHub