History

Zahary Karadjov 7d1efa443d Restore the sync committee pool pruning and add tests		2021-08-30 11:06:45 +03:00
..
README.md	update spec references from eth2.0-specs to consensus-specs and to v1.1.0-beta.2 (#2822 )	2021-08-26 10:21:52 +02:00
attestation_pool.nim	disentangle eth2 types from the ssz library (#2785 )	2021-08-18 20:57:58 +02:00
block_clearance.nim	disentangle eth2 types from the ssz library (#2785 )	2021-08-18 20:57:58 +02:00
block_pools_types.nim	move BeaconClock from ChainDAG to BeaconNode (#2796 )	2021-08-20 08:58:15 +00:00
block_quarantine.nim	rework spec imports (#2779 )	2021-08-12 13:08:20 +00:00
blockchain_dag.nim	sync committee message pool and gossip validation (#2830 )	2021-08-28 10:40:01 +00:00
exit_pool.nim	cleanups (#2809 )	2021-08-24 21:49:51 +02:00
forkedbeaconstate_dbhelpers.nim	forkedbeaconstate_helpers -> forks (#2772 )	2021-08-10 22:46:35 +02:00
spec_cache.nim	update spec references from eth2.0-specs to consensus-specs and to v1.1.0-beta.2 (#2822 )	2021-08-26 10:21:52 +02:00
sync_committee_msg_pool.nim	Restore the sync committee pool pruning and add tests	2021-08-30 11:06:45 +03:00

README.md

Consensus object pools

This folder holds the various consensus object pools needed for a blockchain client.

Object in those pools have passed the "gossip validation" filter according to specs:

blocks: https://github.com/ethereum/consensus-specs/blob/v1.0.1/specs/phase0/p2p-interface.md#beacon_block
aggregate attestations: https://github.com/ethereum/consensus-specs/blob/v1.0.1/specs/phase0/p2p-interface.md#beacon_aggregate_and_proof
unaggregate attestation: https://github.com/ethereum/consensus-specs/blob/v1.0.1/specs/phase0/p2p-interface.md#beacon_attestation_subnet_id
voluntary exits https://github.com/ethereum/consensus-specs/blob/v1.0.1/specs/phase0/p2p-interface.md#voluntary_exit
Attester slashings https://github.com/ethereum/consensus-specs/blob/v1.0.1/specs/phase0/p2p-interface.md#attester_slashing
Proposer slashins https://github.com/ethereum/consensus-specs/blob/v1.0.1/specs/phase0/p2p-interface.md#proposer_slashing

After "gossip validation" the consensus objects can be rebroadcasted as they are optimistically good, however for internal processing further verification is needed. For blocks, this means verifying state transition and all contained cryptographic signatures (instead of just the proposer signature). For other consensus objects, it is possible that gossip validation is a superset of consensus verification (TODO).

The pools presenet in this folder are:

block_pools:
- block_quarantine: for seemingly valid blocks that are on a fork unknown to us.
- block_clearance: to verify (state_transition + cryptography) candidate blocks.
- blockchain_dag: an in-memory direct-acyclic graph of fully validated and verified blockchain candidates with the tail being the last finalized epoch. A block in the DAG MUST be in the fork choice and a block in the fork choice MUST be in the DAG (except for orphans following finalization). On finalization non-empty epoch blocks are stored in the beacon_chain_db.
attestation_pool: Handles the attestation received from gossip and collect them for fork choice.
exit_pool: Handle voluntary exits and forced exits (attester slashings and proposer slashings)