status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-24 13:33:14 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
Etan Kissling 613f4a9a50
accelerate EL sync with LC with --sync-light-client (#4041) 
When the BN-embedded LC makes sync progress, pass the corresponding
execution block hash to the EL via `engine_forkchoiceUpdatedV1`.
This allows the EL to sync to wall slot while the chain DAG is behind.
Renamed `--light-client` to `--sync-light-client` for clarity, and
`--light-client-trusted-block-root` to `--trusted-block-root` for
consistency with `nimbus_light_client`.

Note that this does not work well in practice at this time:
- Geth sticks to the optimistic sync:
  "Ignoring payload while snap syncing" (when passing the LC head)
  "Forkchoice requested unknown head" (when updating to LC head)
- Nethermind syncs to LC head but does not report ancestors as VALID,
  so the main forward sync is still stuck in optimistic mode:
  "Pre-pivot block, ignored and returned Syncing"

To aid EL client teams in fixing those issues, having this available
as a hidden option is still useful.
2022-08-29 12:16:35 +00:00
..
vanity_logs
compatibility with Nim 1.4+ (#3888)
2022-07-29 10:53:42 +00:00
attestation_pool.nim
accelerate EL sync with LC with --sync-light-client (#4041)
2022-08-29 12:16:35 +00:00
block_clearance.nim
withState: state -> forkyState (#4038)
2022-08-26 22:47:40 +00:00
block_dag.nim
update spec ref URLs (#4005)
2022-08-20 16:03:32 +00:00
block_pools_types_light_client.nim
update LC spec references for v1.2.0-rc.2 (#3982)
2022-08-17 19:47:06 +00:00
block_pools_types.nim
cache shuffling separately from other EpochRef data (fixes #2677) (#3990)
2022-08-18 21:07:01 +03:00
block_quarantine.nim
compatibility with Nim 1.4+ (#3888)
2022-07-29 10:53:42 +00:00
blockchain_dag_light_client.nim
withState: state -> forkyState (#4038)
2022-08-26 22:47:40 +00:00
blockchain_dag.nim
adjust checkpoint tracking for devnets (#4039)
2022-08-29 09:26:01 +02:00
consensus_manager.nim
accelerate EL sync with LC with --sync-light-client (#4041)
2022-08-29 12:16:35 +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
update LC spec references for v1.2.0-rc.2 (#3982)
2022-08-17 19:47:06 +00:00
README.md
update spec ref URLs (#3979)
2022-08-17 11:33:19 +00:00
spec_cache.nim
update spec ref URLs (#4005)
2022-08-20 16:03:32 +00:00
sync_committee_msg_pool.nim
Implement a missing ingnore rule for sync committee contributions (#3941)
2022-08-09 12:52:11 +03: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)