History

tersec 19bf460a3b more `withState` `state` -> `forkyState` (#4104 )		2022-09-10 08:12:07 +02:00
..
README.md	state/forkyState cleanup; spec URL updates; rm unused imports (#4052 )	2022-08-31 13:29:34 +02:00
batch_validation.nim	cache shuffling separately from other EpochRef data (fixes #2677 ) (#3990 )	2022-08-18 21:07:01 +03:00
block_processor.nim	more `withState` `state` -> `forkyState` (#4104 )	2022-09-10 08:12:07 +02:00
eth2_processor.nim	update spec ref URLs (#4005 )	2022-08-20 16:03:32 +00:00
gossip_validation.nim	more `withState` `state` -> `forkyState` (#4104 )	2022-09-10 08:12:07 +02:00
light_client_processor.nim	update spec ref URLs (#4005 )	2022-08-20 16:03:32 +00:00
optimistic_processor.nim	reduce LC optsync latency (#4002 )	2022-08-25 03:53:59 +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: