History

Etan Kissling c211a3849e remove `{.raises: [Defect].}` Nim 1.2 compatibility (#5352 ) In Nim 1.6, `{.raises: [Defect].}` is no longer necessary. Remove it.		2023-08-25 11:29:07 +02:00
..
README.md	automated consensus spec URL updating to v1.4.0-beta.1 (#5280 )	2023-08-09 03:58:47 +00:00
batch_validation.nim	fix batch validation when `--num-threads=1` (#5303 )	2023-08-17 10:58:13 +02:00
block_processor.nim	fix/remove remaining fcuV2 in Deneb (#5332 )	2023-08-20 17:35:37 +00:00
eth2_processor.nim	prevent concurrent `storeBlock` calls (fixes #5285 ) (#5295 )	2023-08-17 15:12:37 +02:00
gossip_validation.nim	automated consensus spec URL updating to v1.4.0-beta.1 (#5280 )	2023-08-09 03:58:47 +00:00
light_client_processor.nim	remove `{.raises: [Defect].}` Nim 1.2 compatibility (#5352 )	2023-08-25 11:29:07 +02:00
optimistic_processor.nim	remove `{.raises: [Defect].}` Nim 1.2 compatibility (#5352 )	2023-08-25 11:29:07 +02: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: