History

Etan Kissling 9180f09641 reduce LC optsync latency (#4002 ) The optimistic sync spec was updated since the LC based optsync module was introduced. It is no longer necessary to wait for the justified checkpoint to have execution enabled; instead, any block is okay to be optimistically imported to the EL client, as long as its parent block has execution enabled. Complex syncing logic has been removed, and the LC optsync module will now follow gossip directly, reducing the latency when using this module. Note that because this is now based on gossip instead of using sync manager / request manager, that individual blocks may be missed. However, EL clients should recover from this by fetching missing blocks themselves.		2022-08-25 03:53:59 +00:00
..
README.md	update spec ref URLs (#3979 )	2022-08-17 11:33:19 +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	do not descore peer when EL connection fails (#4020 )	2022-08-24 16:55:41 +00:00
eth2_processor.nim	update spec ref URLs (#4005 )	2022-08-20 16:03:32 +00:00
gossip_validation.nim	update spec ref URLs (#4005 )	2022-08-20 16:03:32 +00: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: