nimbus-eth2/beacon_chain/consensus_object_pools
Jacek Sieka 3cd7cebc7c
Fix block dag pruning frequency (#2469)
Should always prune after finality change but not more than once
2021-04-01 13:26:17 +02:00
..
README.md Consensus object pools [reorg 4/5] (#2374) 2021-03-04 10:13:44 +01:00
attestation_pool.nim increase block proposal speed with many validators (#2423) 2021-03-17 13:35:59 +00:00
block_clearance.nim set upper bound on EpochRef cache (#2403) 2021-03-17 11:17:15 +01:00
block_pools_types.nim Fix minor exception effect issues (#2448) 2021-03-24 17:20:55 +01:00
block_quarantine.nim Consensus object pools [reorg 4/5] (#2374) 2021-03-04 10:13:44 +01:00
blockchain_dag.nim Fix block dag pruning frequency (#2469) 2021-04-01 13:26:17 +02:00
exit_pool.nim centralize p2p validation in a single file and address https://github.com/status-im/nimbus-eth2/pull/2377#issuecomment-791313118 (#2383) 2021-03-06 08:32:55 +01:00
spec_cache.nim use epochref for get_committee_assignments() to avoid repeated shuffling (#2463) 2021-03-30 15:01:47 +00: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:

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)