History

Jacek Sieka 49729e1ef3 prevent concurrent `storeBlock` calls (fixes #5285 ) (#5295 ) When a block is introduced to the system both via REST and gossip at the same time, we will call `storeBlock` from two locations leading to a dupliace check race condition as we wait for the EL. This issue may manifest in particular when using an external block builder that itself publishes the block onto the gossip network. * refactor enqueue flow * simplify calling `addBlock` * complete request manager verifier future for blobless blocks * re-verify parent conditions before adding block among other things, it might have gone stale or finalized between one call and the other		2023-08-17 15:12:37 +02:00
..
README.md	automated consensus spec URL updating to v1.4.0-beta.1 (#5280 )	2023-08-09 03:58:47 +00:00
batch_validation.nim	fix batch validation when `--num-threads=1` (#5303 )	2023-08-17 10:58:13 +02:00
block_processor.nim	prevent concurrent `storeBlock` calls (fixes #5285 ) (#5295 )	2023-08-17 15:12:37 +02:00
eth2_processor.nim	prevent concurrent `storeBlock` calls (fixes #5285 ) (#5295 )	2023-08-17 15:12:37 +02:00
gossip_validation.nim	automated consensus spec URL updating to v1.4.0-beta.1 (#5280 )	2023-08-09 03:58:47 +00:00
light_client_processor.nim	automated consensus spec URL updating to v1.4.0-beta.1 (#5280 )	2023-08-09 03:58:47 +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: