nimbus-eth2/beacon_chain/consensus_object_pools
Etan Kissling 030226148d
rename `exit_pool` > `validator_change_pool` (#5679)
The `ExitPool` was renamed to `ValidatorChangePool` with Capella, but
the files were still using the previous name. Rename for consistency.
2023-12-23 06:55:47 +01:00
..
vanity_logs remove emoji from function names (#5633) 2023-11-29 00:30:44 +00:00
README.md rename `exit_pool` > `validator_change_pool` (#5679) 2023-12-23 06:55:47 +01:00
attestation_pool.nim consensus spec v1.4.0-beta.5 URL updates (#5655) 2023-12-06 22:16:55 +00:00
blob_quarantine.nim track block/blob matching/quarantines using both indices and commitments (#5621) 2023-12-01 18:58:46 +00:00
block_clearance.nim Apply EIP-7044 to block signature batch verification (#5637) 2023-12-01 14:44:45 +00:00
block_dag.nim automated consensus spec URL updating to v1.4.0-beta.5 (#5647) 2023-12-05 03:34:45 +01:00
block_pools_types.nim `blck` --> `forkyBlck` when using `withBlck` / `withStateAndBlck` (#5451) 2023-09-21 12:49:14 +02:00
block_pools_types_light_client.nim restrict best LC update collection to canonical blocks (#5613) 2023-11-21 23:51:05 +01:00
block_quarantine.nim Option[deneb.SignedBeaconBlock] -> Opt[deneb.SignedBeaconBlock] (#5620) 2023-11-24 17:34:45 +01:00
blockchain_dag.nim era: fix verifier at empty slots (#5641) 2023-12-05 07:55:25 +01:00
blockchain_dag_light_client.nim rm unused code (#5623) 2023-11-25 12:09:18 +00:00
consensus_manager.nim Bump nim-web3 to dcabb8f29ee55afedefdf93cd3e102bb1daee354 (#5664) 2023-12-12 22:15:00 +07:00
light_client_pool.nim send LC finality update on event stream on supermajority (#5602) 2023-11-16 19:57:15 -08:00
spec_cache.nim automated consensus spec URL updating to v1.4.0-beta.5 (#5647) 2023-12-05 03:34:45 +01:00
sync_committee_msg_pool.nim consensus spec v1.4.0-beta.5 URL updates (#5672) 2023-12-16 03:27:06 +01:00
validator_change_pool.nim rename `exit_pool` > `validator_change_pool` (#5679) 2023-12-23 06:55:47 +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.
  • validator_change_pool: Handle voluntary exits and forced exits (attester slashings and proposer slashings)