status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-12 22:46:59 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
Etan Kissling 6f466894ab
answer RequestManager queries from disk if possible (#6109) 
When restarting beacon node, orphaned blocks remain in the database but
on startup, only the canonical chain as selected by fork choice loads.
When a new block is discovered that builds on top of an orphaned block,
the orphaned block is re-downloaded using sync/request manager, despite
it already being present on disk. Such queries can be answered locally
to improve discovery speed of alternate forks.
2024-03-21 18:37:31 +01:00
..
vanity_logs
verify genesis_time more strictly (fixes #1667) (#5694)
2024-01-06 15:26:56 +01:00
attestation_pool.nim
automated consensus spec URL updating to v1.4.0 (#6074)
2024-03-14 07:26:36 +01:00
blob_quarantine.nim
Revert "initial Electra support skeleton" (#5955)
2024-02-25 19:42:44 +00:00
block_clearance.nim
make sure clearanceState builds on top of headState in chain stall (#6108)
2024-03-20 16:41:56 +01:00
block_dag.nim
use fixed max depth for BlockRef (#6070)
2024-03-13 13:01:51 +01: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_pools_types.nim
continue validator duties if chain does not progress for a long time (#6101)
2024-03-20 03:23:53 +01:00
block_quarantine.nim
answer RequestManager queries from disk if possible (#6109)
2024-03-21 18:37:31 +01:00
blockchain_dag_light_client.nim
avoid style check issue with syncAggregate (#6013)
2024-03-02 02:54:37 +01:00
blockchain_dag.nim
continue validator duties if chain does not progress for a long time (#6101)
2024-03-20 03:23:53 +01:00
common_tools.nim
Add Keymanager API graffiti endpoints. (#6054)
2024-03-14 03:44:00 +00:00
consensus_manager.nim
continue validator duties if chain does not progress for a long time (#6101)
2024-03-20 03:23:53 +01:00
light_client_pool.nim
verify genesis_time more strictly (fixes #1667) (#5694)
2024-01-06 15:26:56 +01:00
README.md
automated consensus spec URL updating to v1.4.0 (#6074)
2024-03-14 07:26:36 +01:00
spec_cache.nim
automated consensus spec URL updating to v1.4.0 (#6074)
2024-03-14 07:26:36 +01:00
sync_committee_msg_pool.nim
automated consensus spec URL updating to v1.4.0 (#6074)
2024-03-14 07:26:36 +01: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)