nimbus-eth2/beacon_chain/consensus_object_pools
Eugene Kabanov 7319f150e8
Number of REST fixes. (#2987)
* Initial commit.

* Fix path.

* Add validator keys to indices cache mechanism.
Move syncComitteeParticipants to common place.

* Fix sync participants order issue.

* Fix error code when state could not be found.
Refactor `state/validators` to use keysToIndices mechanism.

* Fix RestValidatorIndex to ValidatorIndex conversion TODOs.

* Address review comments.

* Fix REST test rules.
2021-10-14 12:38:38 +02:00
..
README.md update 62 spec URLs to v1.1.2 (#2979) 2021-10-12 10:17:37 +00:00
attestation_pool.nim update 18 spec URLs to v1.1.2; switch from eth2.0-specs to consensus-specs (#2990) 2021-10-14 06:30:21 +00:00
block_clearance.nim implement forked merge state/block support (#2890) 2021-09-27 14:22:58 +00:00
block_pools_types.nim Number of REST fixes. (#2961) 2021-10-06 15:43:03 +02:00
block_quarantine.nim implement forked merge state/block support (#2890) 2021-09-27 14:22:58 +00:00
blockchain_dag.nim Number of REST fixes. (#2987) 2021-10-14 12:38:38 +02:00
exit_pool.nim REST /eth/v1/events API call implementation. (#2878) 2021-09-22 14:17:15 +02:00
forkedbeaconstate_dbhelpers.nim merge hardfork database support (#2911) 2021-09-30 01:07:24 +00:00
spec_cache.nim update 18 spec URLs to v1.1.2; switch from eth2.0-specs to consensus-specs (#2990) 2021-10-14 06:30:21 +00:00
sync_committee_msg_pool.nim use `SyncAggregate.init()` everywhere (#2932) 2021-09-30 13:56:07 +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)