status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-08 20:54:33 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
Jacek Sieka c270ec21e4
Validator monitoring (#2925) 
Validator monitoring based on and mostly compatible with the
implementation in Lighthouse - tracks additional logs and metrics for
specified validators so as to stay on top on performance.

The implementation works more or less the following way:
* Validator pubkeys are singled out for monitoring - these can be
running on the node or not
* For every action that the validator takes, we record steps in the
process such as messages being seen on the network or published in the
API
* When the dust settles at the end of an epoch, we report the
information from one epoch before that, which coincides with the
balances being updated - this is a tradeoff between being correct
(waiting for finalization) and providing relevant information in a
timely manner)
2021-12-20 20:20:31 +01:00
..
attestation_pool.nim
move quarantine outside of chaindag (#3124)
2021-12-06 10:49:01 +01:00
block_clearance.nim
Backfill support for ChainDAG (#3171)
2021-12-13 14:36:06 +01:00
block_dag.nim
BlockId reform (#3176)
2021-12-09 19:06:21 +02:00
block_pools_types.nim
Validator monitoring (#2925)
2021-12-20 20:20:31 +01:00
block_quarantine.nim
move quarantine outside of chaindag (#3124)
2021-12-06 10:49:01 +01:00
blockchain_dag.nim
Validator monitoring (#2925)
2021-12-20 20:20:31 +01:00
exit_pool.nim
Better REST/RPC error messages (#3046)
2021-11-05 17:39:47 +02:00
README.md
v1.1.{5 -> 6} phase 0 and altair spec URL updates (#3157)
2021-12-03 17:40:23 +00:00
spec_cache.nim
v1.1.{5 -> 6} phase 0 and altair spec URL updates (#3157)
2021-12-03 17:40:23 +00:00
sync_committee_msg_pool.nim
batch-verify sync messages for a small perf boost (#3151)
2021-12-09 14:56:54 +02: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)