nimbus-eth2/beacon_chain/consensus_object_pools
Zahary Karadjov 64e791be66
Revert "avoid packing attestations from other forks (#3893)"
This reverts commit 5dcfb0c4e7.
2022-07-27 20:14:40 +03:00
..
vanity_logs cleanups (#3819) 2022-06-29 18:53:59 +02:00
README.md update CL spec URLs (#3690) 2022-06-01 15:52:45 +00:00
attestation_pool.nim Revert "avoid packing attestations from other forks (#3893)" 2022-07-27 20:14:40 +03:00
block_clearance.nim group justified and finalized `Checkpoint` (#3841) 2022-07-06 13:33:02 +03:00
block_clearance_light_client.nim keep track of latest blocks for optimistic sync (#3715) 2022-06-10 14:16:37 +00:00
block_dag.nim group justified and finalized `Checkpoint` (#3841) 2022-07-06 13:33:02 +03:00
block_pools_types.nim group justified and finalized `Checkpoint` (#3841) 2022-07-06 13:33:02 +03:00
block_pools_types_light_client.nim merge LC db into main BN db (#3832) 2022-07-04 23:46:32 +03:00
block_quarantine.nim fix Nim 1.6 build deprecation warnings (#3712) 2022-06-09 12:09:38 +03:00
blockchain_dag.nim rename verifyFinalization internal flag to strictVerification (#3866) 2022-07-13 13:48:09 +00:00
blockchain_dag_light_client.nim rename verifyFinalization internal flag to strictVerification (#3866) 2022-07-13 13:48:09 +00:00
consensus_manager.nim allow driving EL with LC (#3865) 2022-07-14 04:07:40 +00:00
exit_pool.nim group justified and finalized `Checkpoint` (#3841) 2022-07-06 13:33:02 +03:00
light_client_pool.nim update to latest light client libp2p protocol (#3623) 2022-05-23 14:02:54 +02:00
spec_cache.nim rename verifyFinalization internal flag to strictVerification (#3866) 2022-07-13 13:48:09 +00:00
sync_committee_msg_pool.nim bearssl: split abi (#3755) 2022-06-21 10:29:16 +02: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)