status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-09 22:06:21 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
Jacek Sieka ee79c10a7d
update validator key cache on startup (#2760) 
* update validator key cache on startup

Versions prior to 1.1.0 do not write a validator key cache at all.

Versions from 1.4.0 and upwards require an immutable validator key cache
to verify blocks - normally, block verification fills the cache but that
assumes that at least one block was verified by a version that has the
key cache.

Taken together, this breaks direct upgrades from anything <1.1.0 to
1.4.0.

The fix is simply to refresh fill the cache from an existing state on
startup.

* also log serious block validation failures at info level
2021-08-05 11:26:10 +03:00
..
attestation_pool.nim
singe validator key cache
2021-06-01 20:43:44 +03:00
block_clearance.nim
update validator key cache on startup (#2760)
2021-08-05 11:26:10 +03:00
block_pools_types.nim
fix epoch logging (fixes #2283) (#2642)
2021-06-11 01:07:16 +03:00
block_quarantine.nim
singe validator key cache
2021-06-01 20:43:44 +03:00
blockchain_dag.nim
update validator key cache on startup (#2760)
2021-08-05 11:26:10 +03:00
exit_pool.nim
singe validator key cache
2021-06-01 20:43:44 +03:00
README.md
Consensus object pools [reorg 4/5] (#2374)
2021-03-04 10:13:44 +01:00
spec_cache.nim
write uncompressed validator keys to database (#2639)
2021-06-10 10:37:02 +03:00
statedata_helpers.nim
log doppelganger attestation signature; rm withState.HashedBeaconState uses (#2608)
2021-05-28 15:51:15 +03: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)