From bc7d28361b7690371378b046d1a268153d1dd335 Mon Sep 17 00:00:00 2001 From: Mahmud Bello <75342173+mahmudsudo@users.noreply.github.com> Date: Mon, 27 Jan 2025 09:50:03 +0100 Subject: [PATCH] Update 02_consensus.subpage.md (#3959) a misnaming of block to node corrected Co-authored-by: Gabor Greif --- how-it-works/1_protocol/02_consensus.subpage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-it-works/1_protocol/02_consensus.subpage.md b/how-it-works/1_protocol/02_consensus.subpage.md index fbd2412589..6e7b3276df 100644 --- a/how-it-works/1_protocol/02_consensus.subpage.md +++ b/how-it-works/1_protocol/02_consensus.subpage.md @@ -25,7 +25,7 @@ At a high level, a consensus round has the following three phases: - _Block making:_ In every round, at least one node, called a block maker, proposes a block by broadcasting it to all nodes in the subnet using P2P. As we will see, when things go right, there is only one block maker, but sometimes there may be several. -- _Notarization:_ For a block to become _notarized_, at least two thirds of the nodes must validate the node and support its notarization. +- _Notarization:_ For a block to become _notarized_, at least two thirds of the nodes must validate the block and support its notarization. - _Finalization:_ For a block to become _finalized_, at least two thirds of the nodes must support its finalization. As we will see, a node will support the finalization of a block only if it did not support the notarization of any other block, and this simple rule guarantees that if a block is finalized in a given round, then there can be no other notarized block in that round. Let us next look at the different phases of a consensus round in more detail.