nimbus-eth2/beacon_chain/consensus_object_pools
Etan Kissling 88045a91cd
rename new timing metrics, as `_total` suffix is implicit (#5917)
* track latest duration instead of total in new timing metrics

Change `db_checkpoint_seconds` and `state_replay_seconds` metrics to
record the latest duration instead of the total. `nim-metrics` already
synthesizes a `_total` metric from these implicitly.

* still have to use inc, metrics only synthesizes the name not the sum

* prefix with `beacon_dag`
2024-02-20 20:34:41 +01:00
..
vanity_logs verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +01:00
README.md rename `exit_pool` > `validator_change_pool` (#5679) 2023-12-23 06:55:47 +01:00
attestation_pool.nim do not cache zero block hash if block unavailable (#5865) 2024-02-09 22:10:38 +00:00
blob_quarantine.nim implement blob_sidecar Beacon API streaming (#5728) 2024-01-13 11:52:13 +02:00
block_clearance.nim refactor addHeadBlock() to research/ and tests/ helper (#5874) 2024-02-09 23:46:51 +00:00
block_dag.nim verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +01:00
block_pools_types.nim Revert "Revert "fix checkpoint block potentially not getting backfilled into DB (#5863)" (#5871)" (#5875) 2024-02-09 20:44:54 +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_quarantine.nim avoid marking blocks as unviable if `blobless` quarantine is full (#5858) 2024-02-07 13:38:20 +00:00
blockchain_dag.nim rename new timing metrics, as `_total` suffix is implicit (#5917) 2024-02-20 20:34:41 +01:00
blockchain_dag_light_client.nim Revert "Revert "fix checkpoint block potentially not getting backfilled into DB (#5863)" (#5871)" (#5875) 2024-02-09 20:44:54 +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 do not cache zero block hash if block unavailable (#5865) 2024-02-09 22:10:38 +00: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.6 (#5804) 2024-01-20 11:19:47 +00:00
sync_committee_msg_pool.nim automated consensus spec URL updating to v1.4.0-beta.6 (#5804) 2024-01-20 11:19:47 +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)