From eee596ea18ada0c154b78995794ba4ebddc305e4 Mon Sep 17 00:00:00 2001 From: James Ray Date: Fri, 17 Nov 2017 15:54:30 +1100 Subject: [PATCH] this following the specification of [sic] blockchain consensus protocol --- papers/CasperTFG/CasperTFG.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/papers/CasperTFG/CasperTFG.tex b/papers/CasperTFG/CasperTFG.tex index ab65dc7..a1c3ae7 100644 --- a/papers/CasperTFG/CasperTFG.tex +++ b/papers/CasperTFG/CasperTFG.tex @@ -283,7 +283,7 @@ $$ Because this construction satisfies the terms of our consensus safety proof, we know that decisions on such safe estimates in this protocol are consensus safe (if there are less than $t$ Byzantine faults (by weight)). -We have yet to discuss how nodes running the binary consensus protocol can detect when they are in a state with a safe estimate. We discuss this following the specification of blockchain consensus protocol because we detect estimate safety in the same way for both protocols. +We have yet to discuss how nodes running the binary consensus protocol can detect when they are in a state with a safe estimate. We discuss this following the specification of the blockchain consensus protocol because we detect estimate safety in the same way for both protocols. Now that we've covered the binary consensus protocol, it is much simpler to specify the blockchain consensus protocol.