History

Jacek Sieka 4363215a32 relax `BlockRef` database assumptions (#3472 ) * remove `getForkedBlock(BlockRef)` which assumes block data exists but doesn't support archive/backfilled blocks * fix REST `/eth/v1/beacon/headers` request not returning archive/backfilled blocks * avoid re-encoding in REST block SSZ requests (using `getBlockSSZ`)		2022-03-11 13:08:17 +01:00
..
README.md	spec URL & copyright year update (#3338 )	2022-01-29 01:05:39 +00:00
batch_validation.nim	Harden CommitteeIndex, SubnetId, SyncSubcommitteeIndex (#3259 )	2022-01-09 01:28:49 +02:00
block_processor.nim	proc -> func, mainly in spec/state transition and adjecent modules (#3405 )	2022-02-17 11:53:55 +00:00
consensus_manager.nim	proc -> func, mainly in spec/state transition and adjecent modules (#3405 )	2022-02-17 11:53:55 +00:00
eth2_processor.nim	only show setting up doppelganger detection log message if enabled (#3391 )	2022-02-14 19:24:38 +00:00
gossip_validation.nim	relax `BlockRef` database assumptions (#3472 )	2022-03-11 13:08:17 +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: