Skip to content

Commit 7acdc21

Browse files
committed
Typographical corrections
1 parent 945c13c commit 7acdc21

File tree

1 file changed

+23
-14
lines changed

1 file changed

+23
-14
lines changed

docs/understanding-voi/consensus.md

+23-14
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,39 @@
11
# Consensus
22

3-
In order to have blocks selected and written to the Voi blockchain there needs to be a decentralized consensus mechanism.
3+
To have blocks selected and written to the Voi blockchain there needs to be a decentralized consensus mechanism.
44

5-
Voi blockchain is a Pure Proof of Stake (PPoS) network meaning that blocks are selected and written extremely efficiently in a decentralized way to the blockchain by nodes with tokens staked on them through online accounts.
5+
Voi blockchain is a Proof of Stake (PoS) network,
6+
meaning that blocks are selected
7+
and written extremely efficiently in a decentralized way to the blockchain by nodes with tokens
8+
staked on them through online accounts.
69

710
Accounts used in consensus are selected randomly, but with more weight given to accounts that hold more native tokens.
811

9-
There are 3 steps necessary to have a single block written to the blockchain within a given round.
12+
There are three steps necessary to have a single block written to the blockchain within a given round.
1013

1114

1215
### Block Proposal
1316

14-
In this step multiple accounts are selected to propose the new block for the round.
17+
In this step, multiple accounts are selected to propose the new block for the round.
1518

16-
To do this every node in the network runs a pseudorandom function on each account staked on them to determine if an account is selected to propose the block.
19+
To do this,
20+
every node in the network runs a pseudorandom function on each account
21+
staked on them to determine if an account is selected to propose the block.
1722

18-
Once an account is selected by the pseudorandom function, the node that the account is staked on then propagates the proposed block along with proof, the pseudorandom functions output, that the account was selected in a proposal message.
23+
Once an account is selected by the pseudorandom function,
24+
the node that the account is staked on then propagates the proposed block along with proof,
25+
the pseudorandom functions output that the account was selected in a proposal message.
1926

2027
This is so that other nodes in the network can independently verify that the account was actually selected.
2128

22-
2329
### Soft Vote
2430

25-
In this step the nodes select only one proposed block to get certified.
26-
31+
In this step, the nodes select only one proposed block to get certified.
2732

2833
#### Block Propagation
2934

30-
As multiple accounts are selected to propose the new block it means that nodes receive multiple proposal messages. Each proposed block is verified and validated using the proof contained in the proposal message by the nodes.
35+
As multiple accounts are selected to propose the new block, it means that nodes receive multiple proposal messages.
36+
Each proposed block is verified and validated using the proof contained in the proposal message by the nodes.
3137

3238
Only the top ranking proposal message with the lowest score is propagated to other nodes in the network.
3339

@@ -36,7 +42,7 @@ Only the top ranking proposal message with the lowest score is propagated to oth
3642

3743
Each node will then once again run a pseudorandom function on each account staked on it to see if the account is selected to be in the soft vote committee.
3844

39-
For any account that is chosen their voting power is relative to the number of native tokens they hold.
45+
For any account that is chosen, their voting power is relative to the number of native tokens they hold.
4046

4147
The selected accounts vote for the proposal message with the lowest score out of all the proposal messages received by the node after the block propagation. The score is determined in the same way as before using the pseudorandom functions output that is contained in each proposal message to prove the validity of the proposal.
4248

@@ -53,8 +59,11 @@ Now the quorum is reached we proceed to the certify vote step for the block prop
5359

5460
A final committee of accounts selected in the same way as in the soft vote committee now validates the passed block proposal for any problems.
5561

56-
If the block proposal is valid this same final committee votes until a quorum is reached to certify the block in the proposal.
62+
If the block proposal is valid,
63+
this same final committee votes until a quorum is reached to certify the block in the proposal.
5764

58-
Once the block is successfully voted to be certified the node that proposed the block in the first place then creates a certificate for the block and writes it to the ledger.
65+
Once the block is successfully voted to be certified,
66+
the node that proposed the block in the first place then creates a certificate for the block
67+
and writes it to the ledger.
5968

60-
Once the block is written to the ledger a new round begins for the next block.
69+
Once the block is written to the ledger, a new round begins for the next block.

0 commit comments

Comments
 (0)