History

tersec 7c51da037f add block gossip validation condition (#3325 )		2022-01-26 17:22:06 +00: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
batch_validation.nim	Harden CommitteeIndex, SubnetId, SyncSubcommitteeIndex (#3259 )	2022-01-09 01:28:49 +02:00
block_processor.nim	Harden handling of unviable forks (#3312 )	2022-01-26 13:20:08 +01:00
consensus_manager.nim	limit by-root requests to non-finalized blocks (#3293 )	2022-01-21 13:33:16 +02:00
eth2_processor.nim	limit by-root requests to non-finalized blocks (#3293 )	2022-01-21 13:33:16 +02:00
gossip_validation.nim	add block gossip validation condition (#3325 )	2022-01-26 17:22:06 +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: