status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-10 14:26:26 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/gossip_processing
History
Mamy Ratsimbazafy d1cb5b7220
Parallel attestation verification (#2718) 
* Add parallel attestation verification

* Update tests, batchVerify doesn't use the threadpool with only single core (nim-blscurve update)

* bump nim-blscurve

* Debug info for failing eth2 test vectors

* remove submodule eth2-testnets

* verbose debugging of make failure on Windows (libbacktrace?)

* Remove CI debug mode

* initialization convention

* Fix new altair tests
2021-09-17 03:13:52 +03:00
..
batch_validation.nim
Parallel attestation verification (#2718)
2021-09-17 03:13:52 +03: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
Parallel attestation verification (#2718)
2021-09-17 03:13:52 +03:00
gossip_validation.nim
Restore the sync committee pool pruning and add tests
2021-08-30 11:06:45 +03: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

README.md

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.

Security concerns

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

  • from malicious nodes trying to DOS us
  • from long periods of non-finality, creating lots of forks, attestations, forks