status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-24 21:40:03 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/consensus_object_pools
History
Jacek Sieka 20e700fae4
Harden CommitteeIndex, SubnetId, SyncSubcommitteeIndex (#3259) 
* Harden CommitteeIndex, SubnetId, SyncSubcommitteeIndex

Harden the use of `CommitteeIndex` et al to prevent future issues by
using a distinct type, then validating before use in several cases -
datatypes in spec are kept simple though so that invalid data still can
be read.

* fix invalid epoch used in REST
`/eth/v1/beacon/states/{state_id}/committees` committee length (could
return invalid data)
* normalize some variable names
* normalize committee index loops
* fix `RestAttesterDuty` to use `uint64` for `validator_committee_index`
* validate `CommitteeIndex` on ingress in REST API
* update rest rules with stricter parsing
* better REST serializers
* save lots of memory by not using `zip` ...at least a few bytes!
2022-01-09 01:28:49 +02:00
..
attestation_pool.nim
Harden CommitteeIndex, SubnetId, SyncSubcommitteeIndex (#3259)
2022-01-09 01:28:49 +02:00
block_clearance.nim
Handle access to historical data for which there is no state (#3217)
2022-01-05 19:38:04 +01:00
block_dag.nim
REST cleanups (#3255)
2022-01-08 22:06:34 +02:00
block_pools_types.nim
REST cleanups (#3255)
2022-01-08 22:06:34 +02:00
block_quarantine.nim
move quarantine outside of chaindag (#3124)
2021-12-06 10:49:01 +01:00
blockchain_dag.nim
REST cleanups (#3255)
2022-01-08 22:06:34 +02:00
exit_pool.nim
Better REST/RPC error messages (#3046)
2021-11-05 17:39:47 +02:00
README.md
update from phase0/altair v1.1.6 URLs to v1.1.8 spec URLs (#3238)
2022-01-04 03:57:15 +00:00
spec_cache.nim
Harden CommitteeIndex, SubnetId, SyncSubcommitteeIndex (#3259)
2022-01-09 01:28:49 +02:00
sync_committee_msg_pool.nim
Harden CommitteeIndex, SubnetId, SyncSubcommitteeIndex (#3259)
2022-01-09 01:28:49 +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)