nimbus-eth2/beacon_chain/consensus_object_pools
henridf 176c80a3d5
Fix incorrect naming and use of Quarantine.peekBlobless (#4826)
The 'peek' name was incorrect as it was actually removing from the
table. It was consequently used incorrectly in block processing: the
blobless block wasn't returned to the table when it should be.
2023-04-17 18:10:13 +02:00
..
vanity_logs add ANSI art for Deneb 🐟 (#4803) 2023-04-10 12:42:19 +00:00
README.md automated consensus spec URL updating from v1.3.0-rc.4 to rc.5 (#4756) 2023-03-21 00:42:22 +00:00
attestation_pool.nim rename `loadExecutionBlockRoot` > `loadExecutionBlockHash` (#4807) 2023-04-11 16:56:29 +00:00
blob_quarantine.nim Quarantine and reassembly of gossiped blobs and blocks (#4808) 2023-04-13 19:11:40 +00:00
block_clearance.nim rename `stateFork` > `consensusFork` (#4718) 2023-03-11 00:35:52 +00:00
block_dag.nim rename `execution(Block|Payload)Root` > `executionBlockHash` (#4809) 2023-04-11 23:31:47 +00:00
block_pools_types.nim remove most std/options imports (#4778) 2023-03-31 20:46:47 +00: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 Fix incorrect naming and use of Quarantine.peekBlobless (#4826) 2023-04-17 18:10:13 +02:00
blockchain_dag.nim rename `execution(Block|Payload)Root` > `executionBlockHash` (#4809) 2023-04-11 23:31:47 +00:00
blockchain_dag_light_client.nim rename `lcDataForkAtStateFork` > `lcDataForkAtConsensusFork` (#4726) 2023-03-11 20:09:21 +00:00
consensus_manager.nim always use fcUV2 in shapella even for non-proposer fcUs (#4817) 2023-04-17 16:17:52 +02:00
exit_pool.nim don't clear validator change subpools after creating each block (#4704) 2023-03-09 18:19:36 +02: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 assorted consensus spec URL updates to v1.3.0-rc.5 (#4768) 2023-03-27 14:41:22 +00:00
sync_committee_msg_pool.nim automated consensus spec URL updating from v1.3.0-rc.4 to rc.5 (#4756) 2023-03-21 00:42:22 +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)