status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-13 06:57:10 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
Jacek Sieka 89d6a1b403
Introduce slot->BlockRef mapping for finalized chain (#3144) 
* Introduce slot->BlockRef mapping for finalized chain

The finalized chain is linear, thus we can use a seq to lookup blocks by
slot number.

Here, we introduce such a seq, even though in the future, it should
likely be backed by a database structure instead, or, more likely, a
flat era file with a flat lookup index.

This dramatically speeds up requests by slot, such as those coming from
the REST interface or GetBlocksByRange, as these are currently served by
a linear iteration from head.

* fix REST block requests to not return blocks from an earlier slot when
the given slot is empty
* fix StateId interpretation such that it doesn't treat state roots as
block roots
* don't load full block from database just to return its root
2021-12-06 20:52:35 +02:00
..
attestation_pool.nim
move quarantine outside of chaindag (#3124)
2021-12-06 10:49:01 +01:00
block_clearance.nim
move quarantine outside of chaindag (#3124)
2021-12-06 10:49:01 +01:00
block_pools_types.nim
Introduce slot->BlockRef mapping for finalized chain (#3144)
2021-12-06 20:52:35 +02:00
block_quarantine.nim
move quarantine outside of chaindag (#3124)
2021-12-06 10:49:01 +01:00
blockchain_dag.nim
Introduce slot->BlockRef mapping for finalized chain (#3144)
2021-12-06 20:52:35 +02: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
More efficient implementation of the 'POST beacon_committee_subscriptions' API (#3153)
2021-12-03 17:04:58 +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)