From 90cfeb0637ccb3b48e1a3d51063c6b4615e22f67 Mon Sep 17 00:00:00 2001 From: Craig Everett Date: Fri, 6 Feb 2026 20:44:47 +0900 Subject: [PATCH] Update Consensus --- Consensus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Consensus.md b/Consensus.md index 24bc2eb..120f625 100644 --- a/Consensus.md +++ b/Consensus.md @@ -2,7 +2,7 @@ In the context of distributed systems "consensus" means finding some way to agree on a common view of state at a given time. The trouble with the previous sentence is its last word: "[[time]]". There is no absolute notion of "wall clock time" in distributed systems, but it is possible to establish relative sequence in a concrete way. Sequence then becomes the basis for notions of time. This means that sequence is the first thing that must be agreed before anything else can occur. -In blockchain the way this works is that, as mentioned above, a "leader" can be picked, and whatever that leader says can be accepted by all nodes in the system as the agreed truth until that leader is replaced. This reduces the problem of consensus to the problem of leader selection. +In blockchain the way this works is that a "leader" can be picked (see [[Leader (s)election]]), and whatever that leader says can be accepted by all nodes in the system as the agreed truth until that leader is replaced. This reduces the problem of consensus to the problem of leader selection. The Gajumaru works via leader selection as described above, and the mechanism for leader selection on Groot is [PoW](Proof-of-Work). There are other mechanisms of leader selection and also consensus paradigms that do not depend on selection of a single leader.