History

tersec 6b8061b5d6 automated consensus spec URL updating to v1.5.0-alpha.2 (#6279 )		2024-05-09 05:03:10 +00:00
..
README.md	some consensus spec v1.4.0 spec URL updates (#6208 )	2024-04-17 05:51:16 +02:00
batch_validation.nim	raises for gossip (#5808 )	2024-01-22 17:34:54 +01:00
block_processor.nim	automated consensus spec URL updating to v1.5.0-alpha.2 (#6279 )	2024-05-09 05:03:10 +00:00
eth2_processor.nim	explicitly scope AttesterSlashing and IndexedAttestation types to phase0 (#6224 )	2024-04-21 05:49:11 +00:00
gossip_validation.nim	automated consensus spec URL updating to v1.5.0-alpha.2 (#6279 )	2024-05-09 05:03:10 +00:00
light_client_processor.nim	raises for gossip (#5808 )	2024-01-22 17:34:54 +01:00
optimistic_processor.nim	raises for gossip (#5808 )	2024-01-22 17:34:54 +01: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: