Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 02_consensus.subpage.md #3959

Merged
merged 2 commits into from
Jan 27, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion how-it-works/1_protocol/02_consensus.subpage.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading