From afbd29fb8202008f62f863d20cbe218d16cc0d36 Mon Sep 17 00:00:00 2001 From: Tom Date: Sat, 26 Jan 2019 20:30:50 -0600 Subject: [PATCH] Create new section for "consensus" (#33189) * Create new section for "consensus" Added new section for a deeper discussion/dive on consensus as it relates to blockchain * fix: added front matter block --- guide/english/blockchain/consensus/index.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 guide/english/blockchain/consensus/index.md diff --git a/guide/english/blockchain/consensus/index.md b/guide/english/blockchain/consensus/index.md new file mode 100644 index 0000000000..0d7fb068b4 --- /dev/null +++ b/guide/english/blockchain/consensus/index.md @@ -0,0 +1,18 @@ +--- +title: Consensus +--- + +## Consensus +Most discussions of consensus begin with Byzantine Fault Tolerance (BFT). BFT is derived from the Byzantine Generals' Problem, and understanding how it relates to decentralized systems allows for the implementation of other consensus algorithms used today. + +As explained on Wikipedia (https://en.wikipedia.org/wiki/Byzantine_fault_tolerance): + +>A group of generals, each commanding a portion of the Byzantine army, encircle a city. These generals wish to formulate a plan for attacking the city. In its simplest form, the generals must decide only whether to attack or retreat. Some generals may prefer to attack, while others prefer to retreat. The important thing is that every general agree on a common decision, for a halfhearted attack by a few generals would become a rout, and would be worse than either a coordinated attack or a coordinated retreat. + + +## Types of Consensus Algorithms +(See for more: https://hackernoon.com/a-hitchhikers-guide-to-consensus-algorithms-d81aae3eb0e3) + +- Proof of Work +- Proof of Stake +- Proof of Authority