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
Etan Kissling 4e2ffca44a
use fixed max depth for `BlockRef` (#6070) 
In `block_dag` there is a max depth of 100 years configured to detect
internal inconsistencies, e.g., circular references. As `BlockRef` was
changed long ago to only reflect the non-finalized chain segment, the
theoretically supported max depth can be reduced and simplified.
 		2024-03-13 13:01:51 +01:00
..
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-beta.7 spec URL updates (#5945) 2024-02-22 02:42:57 +00:00
attestation_pool.nim rm unused ForkedTrustedBeaconBlock; add some Electra overloads to consensus_object_pools; Electra BeaconBlock gossip support (#5965) 2024-02-26 06:49:12 +00:00
blob_quarantine.nim Revert "initial Electra support skeleton" (#5955) 2024-02-25 19:42:44 +00:00
block_clearance.nim fix EIP-7044 implementation when using batch verification (#5953) 2024-02-25 15:25:26 +01:00
block_dag.nim use fixed max depth for `BlockRef` (#6070) 2024-03-13 13:01:51 +01:00
block_pools_types.nim rm unused ForkedTrustedBeaconBlock; add some Electra overloads to consensus_object_pools; Electra BeaconBlock gossip support (#5965) 2024-02-26 06:49:12 +00: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 Revert "initial Electra support skeleton" (#5955) 2024-02-25 19:42:44 +00:00
blockchain_dag.nim add proposer reward accounting to block transitions (#6022) 2024-03-04 17:00:46 +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 Fix VC not always be able to obtain feeRecipient value. (#5781) 2024-01-19 14:36:04 +00:00
consensus_manager.nim align default `syncHorizon` computation logic across networks (#6066) 2024-03-12 21:51:18 +01:00
light_client_pool.nim verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +01:00
spec_cache.nim automated consensus spec URL updating to v1.4.0-beta.7 (#5942) 2024-02-21 19:44:48 +00:00
sync_committee_msg_pool.nim automated consensus spec URL updating to v1.4.0-beta.7 (#5942) 2024-02-21 19:44:48 +00:00
validator_change_pool.nim verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +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)