History

tersec 0418fbada2 introduce SyncCommitteeMsgPool to eth2_processor and nimbus_beacon_node (#2831 )		2021-08-28 22:27:51 +00:00
..
README.md	update spec references from eth2.0-specs to consensus-specs and to v1.1.0-beta.2 (#2822 )	2021-08-26 10:21:52 +02:00
batch_validation.nim	disentangle eth2 types from the ssz library (#2785 )	2021-08-18 20:57:58 +02:00
block_processor.nim	send attestations and exit messages on fork-appropriate topic (#2773 )	2021-08-19 10:45:31 +00:00
consensus_manager.nim	disentangle eth2 types from the ssz library (#2785 )	2021-08-18 20:57:58 +02:00
eth2_processor.nim	introduce SyncCommitteeMsgPool to eth2_processor and nimbus_beacon_node (#2831 )	2021-08-28 22:27:51 +00:00
gossip_validation.nim	sync committee message pool and gossip validation (#2830 )	2021-08-28 10:40:01 +00: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: