diff --git a/content/_snippets/consensus-q-diagram.html b/content/_snippets/consensus-q-diagram.html index f5a2fdfd18..272bae56c1 100644 --- a/content/_snippets/consensus-q-diagram.html +++ b/content/_snippets/consensus-q-diagram.html @@ -1,97 +1,98 @@
- Each validator proposes a set of transactions to be included in the next ledger version.
-Each also keeps a queue of candidate transactions not currently proposed.
+
+ Each validator proposes a set of transactions to be included in the next ledger version.
+Each also keeps a queue of candidate transactions not currently proposed.
+
- If a validator removes a transaction from its proposal in later rounds, it adds that transaction to its queue.
+
+ If a validator removes a transaction from its proposal in later rounds, it adds that transaction to its queue.
+
- The consensus process continues until enough servers agree on a transaction set.
+
+ The consensus process continues until enough servers agree on a transaction set.
+
- Servers confirm that they built the same resulting ledger and declare it validated.
+
+ Servers confirm that they built the same resulting ledger and declare it validated.
+
- Each validator prepares its proposal for the next ledger version, starting with queued transactions.
+
+ Each validator prepares its proposal for the next ledger version, starting with queued transactions.
+
- If the next proposed ledger is already full, incoming transactions are queued for a later ledger version.
+
+ If the next proposed ledger is already full, incoming transactions are queued for a later ledger version.
+