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
zah a2ba34f686
Implement all sync committee duties in the validator client (#3583) 
Other changes:

* logtrace can now verify sync committee messages and contributions
* Many unnecessary use of pairs() have been removed for consistency
* Map 40x BN response codes to BeaconNodeStatus.Incompatible in the VC
 		2022-05-10 10:03:40 +00:00
..
README.md update unchanged specs/phase0/p2p-interface.md URL references from v1.1.9 to v1.1.10 (#3510) 2022-03-16 10:40:35 +00:00
attestation_pool.nim keep proposer boosting permanently enabled (#3565) 2022-04-12 12:06:30 +02:00
block_clearance.nim stylecheck fixes (#3593) 2022-04-14 17:39:37 +02:00
block_dag.nim kiln beacon node (#3540) 2022-03-25 11:40:10 +00:00
block_pools_types.nim era: load blocks and states (#3394) 2022-03-23 09:58:17 +01:00
block_pools_types_light_client.nim add option to collect light client data (#3474) 2022-03-11 21:28:10 +01:00
block_quarantine.nim Implement all sync committee duties in the validator client (#3583) 2022-05-10 10:03:40 +00:00
blockchain_dag.nim era file verification (#3605) 2022-05-10 03:28:46 +03:00
blockchain_dag_light_client.nim enable `styleCheck:usages` (#3573) 2022-04-08 16:22:49 +00:00
exit_pool.nim proc -> func, mainly in spec/state transition and adjecent modules (#3405) 2022-02-17 11:53:55 +00:00
spec_cache.nim Implement all sync committee duties in the validator client (#3583) 2022-05-10 10:03:40 +00:00
sync_committee_msg_pool.nim automated CL spec ref URL updates from v1.1.9 to v1.1.10 (#3455) 2022-03-02 10:00:21 +00: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)