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 2324136552
add `LightClientHeader` wrapper (#4481) 
The light client data structures were changed to accommodate additional
fields in future forks (e.g., to also hold execution data).

There is a minor change to the JSON serialization, where the `header`
properties are now nested inside a `LightClientHeader`.
The SSZ serialization remains compatible.

See https://github.com/ethereum/consensus-specs/pull/3190
and https://github.com/ethereum/beacon-APIs/pull/287
 		2023-01-13 16:46:35 +01:00
..
vanity_logs display owl on Capella transition (#4442) 2022-12-21 13:30:24 +01:00
README.md consensus spec ref URL updates (#4496) 2023-01-12 13:33:14 +00:00
attestation_pool.nim consensus spec ref URL update v1.3.0-{alpha.2,rc.0}; copyright year update (#4477) 2023-01-09 22:44:44 +00:00
block_clearance.nim Backfill only up to MIN_EPOCHS_FOR_BLOCK_REQUESTS blocks (#4421) 2022-12-23 08:42:55 +01:00
block_dag.nim consensus spec ref URL update v1.3.0-{alpha.2,rc.0}; copyright year update (#4477) 2023-01-09 22:44:44 +00:00
block_pools_types.nim spec: Option -> Opt (#4488) 2023-01-11 12:29:21 +00:00
block_pools_types_light_client.nim make LC data fork aware (#4493) 2023-01-12 18:11:38 +01:00
block_quarantine.nim Blob storage (#4454) 2023-01-09 18:42:10 +00:00
blockchain_dag.nim spec: Option -> Opt (#4488) 2023-01-11 12:29:21 +00:00
blockchain_dag_light_client.nim add `LightClientHeader` wrapper (#4481) 2023-01-13 16:46:35 +01:00
consensus_manager.nim spec: Option -> Opt (#4488) 2023-01-11 12:29:21 +00:00
exit_pool.nim Harden block proposal against expired slashings/exits (#4013) 2022-08-23 18:30:46 +03:00
light_client_pool.nim add `LightClientHeader` wrapper (#4481) 2023-01-13 16:46:35 +01:00
spec_cache.nim consensus spec ref URL update v1.3.0-{alpha.2,rc.0}; copyright year update (#4477) 2023-01-09 22:44:44 +00:00
sync_committee_msg_pool.nim drop subset sync contributions in gossip (#4490) 2023-01-12 15:08:08 +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.
  • exit_pool: Handle voluntary exits and forced exits (attester slashings and proposer slashings)