Git-Mirrors/mev-toolkit
1
0
Fork 0
mirror of https://github.com/autistic-symposium/mev-toolkit.git synced 2025-05-02 06:46:13 -04:00
Code Issues Projects Releases Packages Wiki Activity

🥓 add more dets on validators

Browse source
This commit is contained in:
bt3gl 2022-09-23 05:23:55 -07:00 • committed by GitHub
parent 10ee344a5b
commit 687138aea6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 31 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

59
The-Merge/more-on-validators.md
View file

@ -7,30 +7,17 @@
<br> <br>
- the validator is responsible for creating a new block and sending it out to other nodes on the network. - the validator is responsible for creating a new block and sending it out to other nodes on the network.
- to participate as a validators, a user must deposit 32 ETH into the deposit contract and run 3 pieces of software: - an execution client - a consensus client - a validator - to participate as a validators, a user must deposit 32 ETH into the deposit contract and run 3 pieces of software:
- once activated, validators receive new blocsk from peers - the txs delivered in the block are re-executed, and the block signature is checked - an execution client
- the validator then sends a vote (attestation) in favor of that block across the network - a consensus client
- the engine api
- once activated, validators receive new blocsk from peers (the txs delivered in the block are re-executed, and the block signature is checked).
- the validator then sends a vote (attestation) in favor of that block across the network.
- the timing of blocks is not determined by the mining difficult anymore, but it's fixed: - the timing of blocks is not determined by the mining difficult anymore, but it's fixed:
- slots (12 seconds)
- slots (12 seconds) - epochs (32 slots)
- epochs (32 slots) - in every slot, a committee of validators is randomly chosen, whose votes are used to determine the validity of the block being proposed.
- the first block in each epoch is a checkpoint.
- in every slot, a committee of validators is randomly chosen, whose votes are used to determine the validity of the block being proposed
- the first block in each epoch is a checkpoint
<br>
### setting a dedicated hardware
<br>
* [Check estimate of the blockchain size](https://bitinfocharts.com/ethereum/)
* Minimum specs:
- CPU with 4+ cores
- 32 GB+ RAM
- fast SSD with at least 1T free space
- 25+ MBit/sec download internet service
<br> <br>
@ -40,13 +27,12 @@
The sequence of states that a validator can exist in: The sequence of states that a validator can exist in:
1. deposited: At least 32 ETH has been deposited to the deposit contract by the validator 1. deposited: At least 32 ETH has been deposited to the deposit contract by the validator.
2. pending: the validator is in the activation queue waiting to be voted into the network by existing validators 2. pending: the validator is in the activation queue waiting to be voted into the network by existing validators.
3. active: currently attesting and proposing blocks 3. active: currently attesting and proposing blocks.
4. slashing: the validator has misbehaved and is being slashed 4. slashing: the validator has misbehaved and is being slashed.
5. exiting: the validator has been flagged for exiting the network, either voluntarily or because they have been ejected. 5. exiting: the validator has been flagged for exiting the network, either voluntarily or because they have been ejected.
<br> <br>
### the JSON-RPC interface ### the JSON-RPC interface
@ -58,5 +44,22 @@ The sequence of states that a validator can exist in:
<br> <br>
### setting a dedicated hardware
<br>
* [Check estimate of the blockchain size](https://bitinfocharts.com/ethereum/).
* Minimum specs:
- CPU with 4+ cores
- 32 GB+ RAM
- fast SSD with at least 1T free space
- 25+ MBit/sec download internet service
<br>