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
Jacek Sieka eebc828778
create new database in separate file (#2596) 
The V1 table structure shows great improvements in performance, but if
there's an old `kvstore` without rowid:s, these benefits are nullified:
reorgs during writes and deletes remain expensive (even if the
degradation is reduced somewhat).

This PR creates the tables in a new file instead, and uses the old file
as a read-only store - this has several interesting properties:

* the old database is left completely untouched - this guarantees that
downgrades work smooth (they'll only need to resync their missing
portions)
* starting sync after this PR means only a v1 database is created
* v0 databases stick around - no migration is performed (for now)

Future PR:s can introduce migration of the data from one database to
another - a simply copy will take hours which is downtime we want to
avoid - at that point, it might make sense to migrate straight to era
files instead.
 		2021-05-26 09:07:18 +02:00
..
README.md Consensus object pools [reorg 4/5] (#2374) 2021-03-04 10:13:44 +01:00
attestation_pool.nim use StateData in place of BeaconState outside state transition code (#2551) 2021-05-21 09:23:28 +00:00
block_clearance.nim use StateData in place of BeaconState outside state transition code (#2551) 2021-05-21 09:23:28 +00:00
block_pools_types.nim use StateData in place of BeaconState outside state transition code (#2551) 2021-05-21 09:23:28 +00:00
block_quarantine.nim Consensus object pools [reorg 4/5] (#2374) 2021-03-04 10:13:44 +01:00
blockchain_dag.nim create new database in separate file (#2596) 2021-05-26 09:07:18 +02: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 Perform attestation check before broadcast (#2550) 2021-05-10 09:13:36 +02:00
statedata_helpers.nim use StateData in place of BeaconState outside state transition code (#2551) 2021-05-21 09:23:28 +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)