History

Jacek Sieka 9697b73e71 forkedbeaconstate_helpers -> forks (#2772 ) Simpler module name for stuff that covers forks * check that runtime config matches database state * also include some assorted altair cleanups * use "standard" genesis fork in local testnet to work around missing runtime config support		2021-08-10 22:46:35 +02:00
..
README.md	Reorg (5/5) (#2377 )	2021-03-05 14:12:00 +01:00
batch_validation.nim	remove false OnBlockAdded dependency on phase0 HashedBeaconState (#2661 )	2021-06-21 08:35:24 +00:00
block_processor.nim	forkedbeaconstate_helpers -> forks (#2772 )	2021-08-10 22:46:35 +02:00
consensus_manager.nim	singe validator key cache	2021-06-01 20:43:44 +03:00
eth2_processor.nim	forkedbeaconstate_helpers -> forks (#2772 )	2021-08-10 22:46:35 +02:00
gossip_validation.nim	forkedbeaconstate_helpers -> forks (#2772 )	2021-08-10 22:46:35 +02: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: