History

tersec dfd8cd22b7 bump nim-web3 and use engine API v1.0.0.alpha.9 (#3663 )		2022-05-25 10:30:37 +00:00
..
README.md	update unchanged specs/phase0/p2p-interface.md URL references from v1.1.9 to v1.1.10 (#3510 )	2022-03-16 10:40:35 +00:00
batch_validation.nim	Implement all sync committee duties in the validator client (#3583 )	2022-05-10 10:03:40 +00:00
block_processor.nim	bump nim-web3 and use engine API v1.0.0.alpha.9 (#3663 )	2022-05-25 10:30:37 +00:00
consensus_manager.nim	kiln beacon node (#3540 )	2022-03-25 11:40:10 +00:00
eth2_processor.nim	update to latest light client libp2p protocol (#3623 )	2022-05-23 14:02:54 +02:00
gossip_validation.nim	more CL spec URL updates to v1.2.0-rc.1 (#3657 )	2022-05-24 08:26:35 +00:00
light_client_processor.nim	update to latest light client libp2p protocol (#3623 )	2022-05-23 14:02:54 +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: