Skip to content

Commit 7ee61db

Browse files
committed
fix: fixed section title not displaying correctly
1 parent 4d308c4 commit 7ee61db

File tree

1 file changed

+1
-1
lines changed
  • src/content/developers/docs/consensus-mechanisms/pos/block-proposal

1 file changed

+1
-1
lines changed

src/content/developers/docs/consensus-mechanisms/pos/block-proposal/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Block proposal is part of the proof-of-stake protocol. To help understand this p
1414

1515
Validator accounts propose blocks. Validator accounts are managed by node operators who run validator software as part of their execution and consensus clients and have deposited at least 32 ETH into the deposit contract. However, each validator is only occasionally responsible for proposing a block. Ethereum measures time in slots and epochs. Each slot is twelve seconds, and 32 slots (6.4 minutes) make up an epoch. Every slot is an opportunity to add a new block on Ethereum.
1616

17-
### Random selection {#random-selection}
17+
### Random selection {#random-selection}
1818

1919
A single validator is pseudo-randomly chosen to propose a block in each slot. There is no such thing as true randomness in a blockchain because if each node generated genuinely random numbers, they couldn't come to consensus. Instead, the aim is to make the validator selection process unpredictable. The randomness is achieved on Ethereum using an algorithm called RANDAO that mixes a hash from the block proposer with a seed that gets updated every block. This value is used to select a specific validator from the total validator set. The validator selection is fixed four epochs in advance as a way to protect against certain kinds of seed manipulation.
2020

0 commit comments

Comments
 (0)