499abd927f
* persist LC data across restarts With the Altair spec `LightClientUpdate` structure taking its final form it is finally possible to persist LC data across restarts without having to worry about data migration due to spec changes. A separate `lcdataV1` database is created in the `caches` subdirectory to hold known LC data. A full database with default settings (129 periods) uses <15 MB disk. * extend LC data DB rationale * wording * add `isSupportedBySQLite` helper and explicit return * remove redundant `return` |
||
|---|---|---|
| .. | ||
| vanity_logs | ||
| README.md | ||
| attestation_pool.nim | ||
| block_clearance.nim | ||
| block_clearance_light_client.nim | ||
| block_dag.nim | ||
| block_pools_types.nim | ||
| block_pools_types_light_client.nim | ||
| block_quarantine.nim | ||
| blockchain_dag.nim | ||
| blockchain_dag_light_client.nim | ||
| exit_pool.nim | ||
| light_client_pool.nim | ||
| spec_cache.nim | ||
| sync_committee_msg_pool.nim | ||
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.1.10/specs/phase0/p2p-interface.md#beacon_block
- aggregate attestations: https://github.com/ethereum/consensus-specs/blob/v1.1.10/specs/phase0/p2p-interface.md#beacon_aggregate_and_proof
- unaggregated attestation: https://github.com/ethereum/consensus-specs/blob/v1.2.0-rc.1/specs/phase0/p2p-interface.md#beacon_attestation_subnet_id
- voluntary exits: https://github.com/ethereum/consensus-specs/blob/v1.2.0-rc.1/specs/phase0/p2p-interface.md#voluntary_exit
- Attester slashings: https://github.com/ethereum/consensus-specs/blob/v1.2.0-rc.1/specs/phase0/p2p-interface.md#attester_slashing
- Proposer slashings: https://github.com/ethereum/consensus-specs/blob/v1.2.0-rc.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)