History

Etan Kissling c3d043c0e1 rename `loadExecutionBlockRoot` > `loadExecutionBlockHash` (#4807 ) There are still some `executionBlockRoot` after this, separate rename.		2023-04-11 16:56:29 +00:00
..
README.md	automated consensus spec URL updating from v1.3.0-rc.4 to rc.5 (#4756 )	2023-03-21 00:42:22 +00:00
batch_validation.nim	refactor batch validation not to require genesis_validators_root each time (#4640 )	2023-02-20 09:26:22 +01:00
block_processor.nim	rename `loadExecutionBlockRoot` > `loadExecutionBlockHash` (#4807 )	2023-04-11 16:56:29 +00:00
eth2_processor.nim	Add blob sidecar gossip validation (#4785 )	2023-04-04 15:12:34 +00:00
gossip_validation.nim	rename `loadExecutionBlockRoot` > `loadExecutionBlockHash` (#4807 )	2023-04-11 16:56:29 +00:00
light_client_processor.nim	bump light client spec references to `v1.3.0-rc.3` (#4719 )	2023-03-11 01:11:51 +00:00
optimistic_processor.nim	remove Nim 1.2-compatible `push raise`s and update copyright notice years (#4528 )	2023-01-20 14:14:37 +00:00

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.

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.

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