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
Eugene Kabanov eb6b7affee
Add the `execution_optimistic` flag to REST API responses. (#3780) 
* Initial commit

* Make `events` API spec compliant.

* Add `Eth-Consensus-Version` in responses.

* Bump chronos to get redirect with headers working.

* Add `is_optimistic` field and handling to syncing RestSyncInfo.
 		2022-06-20 08:53:39 +03:00
..
vanity_logs improve panda display (#3732) 2022-06-11 00:48:04 +00:00
README.md update CL spec URLs (#3690) 2022-06-01 15:52:45 +00:00
attestation_pool.nim cleanups: unused and duplicate imports, inconsistent naming conventions, URL updates (#3724) 2022-06-09 14:30:13 +00:00
block_clearance.nim fix missing frontfill index (fixes #3658) (#3675) 2022-05-31 10:09:01 +02:00
block_clearance_light_client.nim keep track of latest blocks for optimistic sync (#3715) 2022-06-10 14:16:37 +00:00
block_dag.nim use ZERO_HASH for default(Eth2Digest)/Eth2Digest() in func calls (#3770) 2022-06-18 04:57:37 +00:00
block_pools_types.nim Add the `execution_optimistic` flag to REST API responses. (#3780) 2022-06-20 08:53:39 +03:00
block_pools_types_light_client.nim rename light client config parameters (#3740) 2022-06-14 12:03:39 +03:00
block_quarantine.nim fix Nim 1.6 build deprecation warnings (#3712) 2022-06-09 12:09:38 +03:00
blockchain_dag.nim Add the `execution_optimistic` flag to REST API responses. (#3780) 2022-06-20 08:53:39 +03:00
blockchain_dag_light_client.nim track LC data section that imported without errors (#3753) 2022-06-19 08:53:10 +03:00
exit_pool.nim fix unnecessary HashList/HashArray cache invalidation (#3660) 2022-05-30 13:30:42 +00:00
light_client_pool.nim update to latest light client libp2p protocol (#3623) 2022-05-23 14:02:54 +02:00
spec_cache.nim more CL spec URL updates to v1.2.0-rc.1 (#3657) 2022-05-24 08:26:35 +00:00
sync_committee_msg_pool.nim CL spec URL updates to v1.2.0-rc.1 (#3655) 2022-05-23 19:30:24 +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)