mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-12 22:46:59 +00:00

History

One more step on the journey to reduce `BlockRef` usage across the
codebase - this one gets rid of `StateData` whose job was to keep track
of which block was last assigned to a state - these duties have now been
taken over by `latest_block_root`, a fairly recent addition that
computes this block root from state data (at a small cost that should be
insignificant)

99% mechanical change.

2022-03-16 08:20:40 +01:00

batch_validation.nim

Harden CommitteeIndex, SubnetId, SyncSubcommitteeIndex (#3259 )

2022-01-09 01:28:49 +02:00

block_processor.nim

remove StateData (#3507 )

2022-03-16 08:20:40 +01:00

consensus_manager.nim

proc -> func, mainly in spec/state transition and adjecent modules (#3405 )

2022-02-17 11:53:55 +00:00

eth2_processor.nim

libp2p light client gossip validation (#3486 )

2022-03-14 14:05:38 +01:00

gossip_validation.nim

remove StateData (#3507 )

2022-03-16 08:20:40 +01:00

README.md

spec URL & copyright year update (#3338 )

2022-01-29 01:05:39 +00:00

README.md

Gossip Processing

This folder holds a collection of modules to:

validate raw gossip data before
- rebroadcasting it (potentially aggregated)
- sending it to one of the consensus object pools

Validation

Gossip validation is different from consensus verification in particular for blocks.

Blocks: https://github.com/ethereum/consensus-specs/blob/v1.1.9/specs/phase0/p2p-interface.md#beacon_block
Attestations (aggregated): https://github.com/ethereum/consensus-specs/blob/v1.1.9/specs/phase0/p2p-interface.md#beacon_aggregate_and_proof
Attestations (unaggregated): https://github.com/ethereum/consensus-specs/blob/v1.1.9/specs/phase0/p2p-interface.md#attestation-subnets
Voluntary exits: https://github.com/ethereum/consensus-specs/blob/v1.1.9/specs/phase0/p2p-interface.md#voluntary_exit
Proposer slashings: https://github.com/ethereum/consensus-specs/blob/v1.1.9/specs/phase0/p2p-interface.md#proposer_slashing
Attester slashing: https://github.com/ethereum/consensus-specs/blob/v1.1.9/specs/phase0/p2p-interface.md#attester_slashing

There are multiple consumers of validated consensus objects:

a ValidationResult.Accept output triggers rebroadcasting in libp2p
- We jump into method validate(PubSub, Message) in libp2p/protocols/pubsub/pubsub.nim
- which was called by rpcHandler(GossipSub, PubSubPeer, RPCMsg)
a blockValidator message enqueues the validated object to the processing queue in block_processor
- blockQueue: AsyncQueue[BlockEntry] (shared with request_manager and sync_manager)
- This queue is then regularly processed to be made available to the consensus object pools.
a xyzValidator message adds the validated object to a pool in eth2_processor
- Attestations (unaggregated and aggregated) get collected into batches.
- Once a threshold is exceeded or after a timeout, they get validated together using BatchCrypto.

Security concerns

As the first line of defense in Nimbus, modules must be able to handle bursts of data that may come:

from malicious nodes trying to DOS us
from long periods of non-finality, creating lots of forks, attestations