History

Jacek Sieka bf6ad41d7d add drop and sync committee metrics * use storeBlock for processing API blocks * avoid double block dump * count all gossip metrics at the same spot * simplify block broadcast		2021-10-20 18:20:12 +03:00
..
README.md	update 27 spec URLs to v1.1.2 (#2989 )	2021-10-13 16:49:06 +00:00
batch_validation.nim	import cleanup (#2997 )	2021-10-19 16:09:26 +02:00
block_processor.nim	add drop and sync committee metrics	2021-10-20 18:20:12 +03:00
consensus_manager.nim	disentangle eth2 types from the ssz library (#2785 )	2021-08-18 20:57:58 +02:00
eth2_processor.nim	add drop and sync committee metrics	2021-10-20 18:20:12 +03:00
gossip_validation.nim	add drop and sync committee metrics	2021-10-20 18:20:12 +03: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
- blocksQueue: 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: