nimbus-eth2/beacon_chain/consensus_object_pools
tersec dc0bbe3a57
rm blockForkAtEpoch and switch callers to consensusForkAtEpoch (#4634)
2023-02-16 21:16:54 +01:00
..
vanity_logs remove Nim 1.2-compatible `push raise`s and update copyright notice years (#4528) 2023-01-20 14:14:37 +00:00
README.md automated v1.3.0-rc.1 to v1.3.0-rc.2 consensus spec URL updates (#4568) 2023-01-31 00:26:57 +01:00
attestation_pool.nim pass correct CI test flag to initializer (#4621) 2023-02-14 14:51:24 +01:00
block_clearance.nim `BeaconStateFork/BeaconBlockFork` -> `ConsensusFork` (#4560) 2023-01-28 19:53:41 +00:00
block_dag.nim prioritize REST API-provided BLS to execution changes over gossip-received changes (#4580) 2023-02-03 16:28:28 +01:00
block_pools_types.nim seed sync committee state cache (#4592) 2023-02-07 11:22:22 +01:00
block_pools_types_light_client.nim remove Nim 1.2-compatible `push raise`s and update copyright notice years (#4528) 2023-01-20 14:14:37 +00:00
block_quarantine.nim remove unused phase0/altair-specific REST deserialization (#4605) 2023-02-13 12:03:38 +01:00
blockchain_dag.nim rm blockForkAtEpoch and switch callers to consensusForkAtEpoch (#4634) 2023-02-16 21:16:54 +01:00
blockchain_dag_light_client.nim `BeaconStateFork/BeaconBlockFork` -> `ConsensusFork` (#4560) 2023-01-28 19:53:41 +00:00
consensus_manager.nim Implement the set of gas_limit end-points in the Keymanager API (#4612) 2023-02-15 15:10:31 +00:00
exit_pool.nim prioritize REST API-provided BLS to execution changes over gossip-received changes (#4580) 2023-02-03 16:28:28 +01:00
light_client_pool.nim remove Nim 1.2-compatible `push raise`s and update copyright notice years (#4528) 2023-01-20 14:14:37 +00:00
spec_cache.nim automated v1.3.0-rc.1 to v1.3.0-rc.2 consensus spec URL updates (#4568) 2023-01-31 00:26:57 +01:00
sync_committee_msg_pool.nim automated v1.3.0-rc.1 to v1.3.0-rc.2 consensus spec URL updates (#4568) 2023-01-31 00:26:57 +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)