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
tersec 2b2846b468
implement forked merge state/block support (#2890) 
* implement forked state/block support

* merge support for containsOrphan; import cleanup; 80-column lines

* add merge block header operations and slot sanity fixture

* add epoch state transition tests; implement is_valid_gas_limit(), is_merge_block(), is_execution_enabled(), and compute_timestamp_at_slot()

* implement process_execution_payload() and add merge deposit operations tests

* add merge block sanity tests

* add merge case to syncCommitteeParticipants

* v1.1.0-beta.5 updates

* reduce getTestStates-based memory usage; don't try to REST-serialize ExecutionPayload transactions without underlying support

* add execution payload tests; switch var to let in tests/official/
2021-09-27 14:22:58 +00:00
..
attestation_pool.nim
implement forked merge state/block support (#2890)
2021-09-27 14:22:58 +00:00
block_clearance.nim
implement forked merge state/block support (#2890)
2021-09-27 14:22:58 +00:00
block_pools_types.nim
implement forked merge state/block support (#2890)
2021-09-27 14:22:58 +00:00
block_quarantine.nim
implement forked merge state/block support (#2890)
2021-09-27 14:22:58 +00:00
blockchain_dag.nim
implement forked merge state/block support (#2890)
2021-09-27 14:22:58 +00:00
exit_pool.nim
REST /eth/v1/events API call implementation. (#2878)
2021-09-22 14:17:15 +02:00
forkedbeaconstate_dbhelpers.nim
implement forked merge state/block support (#2890)
2021-09-27 14:22:58 +00:00
README.md
update spec references from eth2.0-specs to consensus-specs and to v1.1.0-beta.2 (#2822)
2021-08-26 10:21:52 +02:00
spec_cache.nim
fixes (#2901)
2021-09-27 11:24:58 +02:00
sync_committee_msg_pool.nim
REST /eth/v1/events API call implementation. (#2878)
2021-09-22 14:17:15 +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)