How The Hotstuff Protocol is NOT Secure?

Each participant stores a tree of pending commands locally, in addition to the state variables viewNumber (starting at 1, stores the highest QC it voted to pre-commit), and prepareQC (starts at nil), lockedQC (starts at nil, stores the highest QC it voted to commit). When a “new-view” or round starts, a public function determines the leader from the current participants.

Read the full story

Via https://hackernoon.com/how-the-hotstuff-protocol-is-not-secure-gf9a32mv?source=rss