status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
tersec 40616b6243
update some consensus spec URLs to v1.4.0-beta.2 (#5497) 		2023-10-12 05:07:41 +00:00
..
vanity_logs remove `{.raises: [Defect].}` Nim 1.2 compatibility (#5352) 2023-08-25 11:29:07 +02:00
README.md update some consensus spec URLs to v1.4.0-beta.2 (#5497) 2023-10-12 05:07:41 +00:00
attestation_pool.nim avoid needlessly rescoring aggregates during block attestation packing (#5471) 2023-10-04 22:38:10 +00:00
blob_quarantine.nim ensure blob quarantine insertion always succeeds (#5369) 2023-08-29 16:46:25 +00:00
block_clearance.nim propagate newPayload-VALID to block ancestors (#5343) 2023-08-23 19:56:35 +00:00
block_dag.nim automated consensus spec URL updating to v1.4.0-beta.1 (#5280) 2023-08-09 03:58:47 +00: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 remove `{.raises: [Defect].}` Nim 1.2 compatibility (#5352) 2023-08-25 11:29:07 +02:00
block_quarantine.nim Perform block pre-check before validating execution (#5169) 2023-07-11 18:55:51 +02:00
blockchain_dag.nim ShufflingRef approach to next-epoch validator duty calculation/prediction (#5414) 2023-10-10 00:02:07 +00:00
blockchain_dag_light_client.nim reduce redundant zero initialization for LC data objects (#5479) 2023-10-04 18:11:45 +02:00
consensus_manager.nim `validator_duties`->`beacon_validators` (#5333) 2023-08-23 19:39:57 +03:00
exit_pool.nim convert remaining `toFork` -> `kind` for consistency (#5462) 2023-09-27 15:10:28 +00: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 update some consensus spec URLs to v1.4.0-beta.2 (#5497) 2023-10-12 05:07:41 +00:00
sync_committee_msg_pool.nim remove `{.raises: [Defect].}` Nim 1.2 compatibility (#5352) 2023-08-25 11:29:07 +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)