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
Jacek Sieka f90b2b8b1f
reward accounting for altair+ (#2981) 
Similar to the existing `RewardInfo`, this PR adds the infrastructure
needed to export epoch processing information from altair+. Because
accounting is done somewhat differently, the PR uses a fork-specific
object to extrct the information in order to make the cost on the spec
side low.

* RewardInfo -> EpochInfo, ForkedEpochInfo
* use array for computing new sync committee
* avoid repeated total active balance computations in block processing
* simplify proposer index check
* simplify epoch transition tests
* pre-compute base increment and reuse in epoch processing, and a few
other small optimizations

This PR introduces the type and does the heavy lifting in terms of
refactoring - the tools that use the accounting will need separate PR:s
(as well as refinements to the exportred information)
 		2021-10-13 16:24:36 +02:00
..
README.md update 62 spec URLs to v1.1.2 (#2979) 2021-10-12 10:17:37 +00:00
attestation_pool.nim use forked `getAttestationsForBlock` everywhere (#2937) 2021-10-01 01:29:32 +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 reward accounting for altair+ (#2981) 2021-10-13 16:24:36 +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 62 spec URLs to v1.1.2 (#2979) 2021-10-12 10:17:37 +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)