nimbus-eth2/beacon_chain/consensus_object_pools
Jacek Sieka aa1dea03cd
speed up gossip and sync block validation (#3143)
* avoid recomputing hash for block signature check
* check block slot match before hitting the database
2021-12-01 10:52:40 +01:00
..
README.md a dozen spec URL updates to v1.1.5 (#3078) 2021-11-10 08:12:41 +00:00
attestation_pool.nim Fork choice EF consensus tests (#3041) 2021-11-25 19:41:39 +01:00
block_clearance.nim Better REST/RPC error messages (#3046) 2021-11-05 17:39:47 +02:00
block_pools_types.nim Speed up altair block processing 2x (#3115) 2021-11-24 13:43:50 +01:00
block_quarantine.nim altair fork handling cleanups (#3050) 2021-11-05 08:34:34 +01:00
blockchain_dag.nim speed up gossip and sync block validation (#3143) 2021-12-01 10:52:40 +01:00
exit_pool.nim Better REST/RPC error messages (#3046) 2021-11-05 17:39:47 +02:00
spec_cache.nim mass/mechanical update of 1.1.4 phase0 and altair spec URLs to 1.1.5 (#3067) 2021-11-09 07:40:41 +00:00
sync_committee_msg_pool.nim Cleanups (#3123) 2021-11-25 13:20:36 +01: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)