History

Jacek Sieka 6e2a02466e unify bn/vc doppelganger detection (#4398 ) * fix REST liveness endpoint responding even when gossip is not enabled * fix VC exit code on doppelganger hit * fix activation epoch not being updated correctly on long deposit queues * fix activation epoch being set incorrectly when updating validator * move most implementation logic to `validator_pool`, add tests * ensure consistent logging between VC and BN * add docs		2022-12-09 17:05:55 +01:00
..
README.md	EIP4844 tweaks to pass SSZ consensus object tests (#4390 )	2022-12-05 21:36:53 +00: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	`withUpdatedState` injects `updatedState` rather than `state` template (#4375 )	2022-11-30 16:37:23 +02:00
eth2_processor.nim	unify bn/vc doppelganger detection (#4398 )	2022-12-09 17:05:55 +01:00
gossip_validation.nim	eip4844 fork and epoch transition tests; some eip4844 gossip (#4393 )	2022-12-06 16:43:11 +00:00
light_client_processor.nim	add hooks for observing LC progress (#4401 )	2022-12-08 16:24:16 +00:00
optimistic_processor.nim	rm optimistic candidate block check from LC (#4131 )	2022-09-17 00:42:19 +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: