nimbus-eth2/beacon_chain/consensus_object_pools
Agnish Ghosh 6fc5fc79ed
have gather data columns in enqueue block
2024-10-13 13:48:51 +05:30
..
vanity_logs verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +01:00
README.md some consensus spec v1.4.0 spec URL updates (#6215) 2024-04-18 03:00:04 +02:00
attestation_pool.nim electra attestation updates (#6295) 2024-05-17 15:37:41 +03:00
blob_quarantine.nim add Electra blob support to block/blob quarantines, block processor, and request manager (#6201) 2024-04-11 09:31:39 +00:00
block_clearance.nim add branch discovery module for supporting chain stall situation (#6125) 2024-03-24 08:41:47 +00:00
block_dag.nim fix most ConvFromXtoItselfNotNeeded hints and unhide remaining ones (#6307) 2024-05-22 13:56:37 +02:00
block_pools_types.nim add Electra to ConsensusFork enum (#6169) 2024-04-03 16:43:43 +02:00
block_pools_types_light_client.nim track latest `LightClientUpdate` only once fork choice selects it (#5691) 2024-01-03 23:36:05 +01:00
block_quarantine.nim add: forward and backward syncing for data columns, broadcasting data columns created from blobs, added dc support to sync_queue 2024-06-24 17:32:06 +05:30
blockchain_dag.nim automated consensus spec URL updating to v1.5.0-alpha.2 (#6279) 2024-05-09 05:03:10 +00:00
blockchain_dag_light_client.nim avoid style check issue with `syncAggregate` (#6013) 2024-03-02 02:54:37 +01:00
common_tools.nim Add Keymanager API graffiti endpoints. (#6054) 2024-03-14 03:44:00 +00:00
consensus_manager.nim block_sim runs electra (#6181) 2024-04-07 09:58:11 +02:00
data_column_quarantine.nim have gather data columns in enqueue block 2024-10-13 13:48:51 +05:30
light_client_pool.nim verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +01:00
spec_cache.nim rm debugRaiseAssert; clean up several debugComments (#6308) 2024-05-23 23:51:09 +02:00
sync_committee_msg_pool.nim automated consensus spec URL updating to v1.5.0-alpha.2 (#6279) 2024-05-09 05:03:10 +00:00
validator_change_pool.nim explicitly scope AttesterSlashing and IndexedAttestation types to phase0 (#6224) 2024-04-21 05:49:11 +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.
  • validator_change_pool: Handle voluntary exits and forced exits (attester slashings and proposer slashings)