Skip to content

Commit

Permalink
Update EIP-2982: Fix typos (ethereum#8394)
Browse files Browse the repository at this point in the history
Signed-off-by: clonefetch <c0217@outlook.com>
  • Loading branch information
clonefetch authored Apr 24, 2024
1 parent b82250d commit 9b0a632
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions EIPS/eip-2982.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ In addition to the above, PoS has synergies with the sharding scaling solution.

## Specification

Phase 0 is designed to require _no breaking consensus changes_ to existing Ethereum mainnet. Instead, this is the bootstraping a new PoS consensus that can, once stable, supplant the current PoW consensus.
Phase 0 is designed to require _no breaking consensus changes_ to existing Ethereum mainnet. Instead, this is the bootstrapping a new PoS consensus that can, once stable, supplant the current PoW consensus.

Phase 0 specifications are maintained in a repository independent of this EIP. `SPEC_RELEASE_VERSION` release of the specs at `SPEC_RELEASE_COMMIT` are considered the canonical Phase 0 specs for this EIP.

Expand Down Expand Up @@ -394,7 +394,7 @@ The deposit contract maintains a Merkle root of all deposits made so far. Once a

#### Activation

The validator immediately joins the validator registry, but is at first inactive. The validator becomes active after $N \ge 4$ epochs; the minimum of 4 is there to ensure the RANDAO is not manipulable, and $N$ may exceed 4 if too many validators try to join at the same time. If the active validator set has size $|V|$, a maximum of $max(4, \frac{|V|}{65536})$ valdators can join per epoch; if more validators try to join, they are put in a queue and processed as quickly as possible.
The validator immediately joins the validator registry, but is at first inactive. The validator becomes active after $N \ge 4$ epochs; the minimum of 4 is there to ensure the RANDAO is not manipulable, and $N$ may exceed 4 if too many validators try to join at the same time. If the active validator set has size $|V|$, a maximum of $max(4, \frac{|V|}{65536})$ validators can join per epoch; if more validators try to join, they are put in a queue and processed as quickly as possible.

#### Exiting

Expand Down

0 comments on commit 9b0a632

Please sign in to comment.