History

Mamy Ratsimbazafy c47d636cb3 Split Eth2Processor in prep for batching (#2396 ) * Split Eth2Processor in gossip and consensus part and materialize the shared block queue * Update initialization in test_sync_manager		2021-03-11 11:10:57 +01:00
..
README.md	Reorg (5/5) (#2377 )	2021-03-05 14:12:00 +01:00
consensus_manager.nim	Split Eth2Processor in prep for batching (#2396 )	2021-03-11 11:10:57 +01:00
eth2_processor.nim	Split Eth2Processor in prep for batching (#2396 )	2021-03-11 11:10:57 +01:00
gossip_to_consensus.nim	Split Eth2Processor in prep for batching (#2396 )	2021-03-11 11:10:57 +01:00
gossip_validation.nim	centralize p2p validation in a single file and address https://github.com/status-im/nimbus-eth2/pull/2377#issuecomment-791313118 (#2383 )	2021-03-06 08:32:55 +01:00

Gossip Processing

This folders hold a collection of modules to:

validate raw gossip data before
- rebroadcasting them (potentially aggregated)
- sending it to one of the consensus object pool

Validation

Gossip Validation is different from consensus verification in particular for blocks.

There are 2 consumers of validated consensus objects:

a ValidationResult.Accept output triggers rebroadcasting in libp2p
- method validate(PubSub, message) in libp2p/protocols/pubsub/pubsub.nim in the
- which was called by rpcHandler(GossipSub, PubSubPeer, RPCMsg)
a xyzValidator message enqueues the validated object in one of the processing queue in eth2_processor
- blocksQueue: AsyncQueue[BlockEntry], (shared with request_manager and sync_manager)
- attestationsQueue: AsyncQueue[AttestationEntry]
- aggregatesQueue: AsyncQueue[AggregateEntry]

Those queues are then regularly processed to be made available to the consensus object pools.

As the first line of defense in Nimbus, modules must be able to handle burst of data that may come: