Skip to content

Latest commit

 

History

History
27 lines (17 loc) · 1.83 KB

File metadata and controls

27 lines (17 loc) · 1.83 KB
description
Allows an honest and reliable quorum of validators to quickly aggregate the required number of signatures in a distributed manner, allowing the algorithm to scale to large numbers of validators.

BFTree

(BFtreee) ... enable a more decentralized proof-of-stake protocol by eliminating the need for two classes of nodes and delegation to a small number of validators. We view the goal of scaling to millions of validators as a forcing function to create a more scalable consensus
algorithm where BFT is no longer the bottleneck in terms of
making cryptocurrencies more decentralized. In practice, other bottlenecks, such as block sizes, may make the ideal number of validators be tens or hundreds of thousands of nodes for large cryptocurrencies.

BFTree arranges validators into a virtual tree, to parallelize signature aggregation between non-byzantine nodes working to achieve consensus. When byzantine nodes interfere with the aggregation, the roots of all subtrees that were able to achieve agreement perform BFT consensus to finish the round, frequently with fewer messages than if all validators participated. By thoughtfully reorganizing the tree such that nodes that have historically been reliable are paired with other reliable nodes, BFTree limits the impact that a byzantine node can have. Source: https://medium.com/celohq/bftree-scaling-hotstuff-to-millions-of-validators-7d6930ee046a

A step by step example of how BFTree achieves consensus in the presence of faulty validators.

Whitepaper

Used in