From d5fb5e938ecdadf6e5c027cb6b99320a2bc782b7 Mon Sep 17 00:00:00 2001 From: pdobacz Date: Wed, 11 May 2016 17:39:50 +0200 Subject: [PATCH] Update hc_consensus_explained.md Added a third scenario where validator can unlock (NoQuorum) for consistency --- hc_consensus_explained.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hc_consensus_explained.md b/hc_consensus_explained.md index fce2419..bc975a9 100644 --- a/hc_consensus_explained.md +++ b/hc_consensus_explained.md @@ -92,7 +92,7 @@ As long as a node is locked it must not vote for another block on H. A node is - it is NotLocked (i.e. it had not seen a valid proposal and timed out in the previous round) or - it received a VoteInstruction (which proves that +1/3 of the nodes are already locked on a different block) - + - it received a valid proposal H,R with a NoQuorum(R-1) LockSet, for R > R0 Nodes must vote in every round (e.g. repeating older votes but signed for the new round)