status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-25 05:49:26 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/gossip_processing
History
tersec 317b6de4e6
send attestations and exit messages on fork-appropriate topic (#2773) 
* send attestations and exit messages on fork-appropriate topic

* document why use wall clock over attestation slot

* centralize some fork-topic-picking-logic in eth2_network

* pick up new test in summary

* allow specified GetTimeFn for testing purposes

* add GenesisTime and use it in eth2_network

* replace GetTimeFn and GenesisTime with GetBeaconTimeFn
2021-08-19 10:45:31 +00: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
send attestations and exit messages on fork-appropriate topic (#2773)
2021-08-19 10:45:31 +00:00
gossip_validation.nim
disentangle eth2 types from the ssz library (#2785)
2021-08-18 20:57:58 +02:00
README.md
Reorg (5/5) (#2377)
2021-03-05 14:12:00 +01: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