History

tersec 54cc7bb7a1 update some consensus-spec URLs to v1.4.0-alpha.3 (#5074 )		2023-06-13 21:07:39 +00:00
..
README.md	update some consensus-spec URLs to v1.4.0-alpha.3 (#5074 )	2023-06-13 21:07:39 +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	https://github.com/ethereum/consensus-specs/pull/3359 (#5047 )	2023-06-10 05:39:10 +00:00
eth2_processor.nim	automated v1.4.0-alpha.2 to v1.4.0-alpha.3 consensus spec URL updates (#5065 )	2023-06-13 14:03:49 +00:00
gossip_validation.nim	update some consensus-spec URLs to v1.4.0-alpha.3 (#5074 )	2023-06-13 21:07:39 +00:00
light_client_processor.nim	automated v1.4.0-alpha.2 to v1.4.0-alpha.3 consensus spec URL updates (#5065 )	2023-06-13 14:03:49 +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: