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
tersec 79bb0d5379
only deserialize attestation and aggregation gossiped signatures once (#2472) 
* only deserialize attestation and aggregation gossiped signatures once

* re-indent some aggregate checks into block scope

* spelling

* remove debugging assertion

* put part of gossip validation back into block context

* attestation pool test signature loading isn't so unsafe, and exportRaw isn't free

* remove more development doAsserts; don't exportRaw in loops
 		2021-04-09 14:59:24 +02:00
..
README.md Consensus object pools [reorg 4/5] (#2374) 2021-03-04 10:13:44 +01:00
attestation_pool.nim only deserialize attestation and aggregation gossiped signatures once (#2472) 2021-04-09 14:59:24 +02:00
block_clearance.nim remove some BeaconState use and abstract over other uses (#2482) 2021-04-08 08:24:25 +00:00
block_pools_types.nim add Altair domains and participation flags; clean up imports (#2462) 2021-04-04 16:24:45 +00:00
block_quarantine.nim Consensus object pools [reorg 4/5] (#2374) 2021-03-04 10:13:44 +01:00
blockchain_dag.nim remove some BeaconState use and abstract over other uses (#2482) 2021-04-08 08:24:25 +00:00
exit_pool.nim remove some BeaconState use and abstract over other uses (#2482) 2021-04-08 08:24:25 +00:00
spec_cache.nim use epochref for get_committee_assignments() to avoid repeated shuffling (#2463) 2021-03-30 15:01:47 +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)