status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-14 08:36:53 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/gossip_processing
History
tersec 3a818ecb93
fall back to non-fcu fork choice on epoch boundaries (#5195) 
* fall back to non-fcu fork choice on epoch boundaries

* Future[bool]

* fix

* Update beacon_chain/consensus_object_pools/consensus_manager.nim

Co-authored-by: Etan Kissling <etan@status.im>

* make things consistent with Opt[void] return

---------

Co-authored-by: Etan Kissling <etan@status.im>
2023-07-17 22:30:38 +02:00
..
batch_validation.nim
refactor batch validation not to require genesis_validators_root each time (#4640)
2023-02-20 09:26:22 +01:00
block_processor.nim
fall back to non-fcu fork choice on epoch boundaries (#5195)
2023-07-17 22:30:38 +02:00
eth2_processor.nim
automated consensus spec URL updating to v1.4.0-beta.0 (#5121)
2023-06-24 15:43:30 +00:00
gossip_validation.nim
Perform block pre-check before validating execution (#5169)
2023-07-11 18:55:51 +02:00
light_client_processor.nim
automated consensus spec URL updating to v1.4.0-beta.0 (#5121)
2023-06-24 15:43:30 +00:00
optimistic_processor.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00
README.md
update some consensus-specs ref URLs to v1.4.0-beta.0 (#5163)
2023-07-05 16:02:55 +00:00

README.md

Gossip Processing

This folder holds a collection of modules to:

  • validate raw gossip data before
    • rebroadcasting it (potentially aggregated)
    • sending it to one of the consensus object pools

Validation

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

There are multiple consumers of validated consensus objects:

  • a ValidationResult.Accept output triggers rebroadcasting in libp2p
    • We jump into method validate(PubSub, Message) in libp2p/protocols/pubsub/pubsub.nim
    • which was called by rpcHandler(GossipSub, PubSubPeer, RPCMsg)
  • a blockValidator message enqueues the validated object to the processing queue in block_processor
    • blockQueue: AsyncQueue[BlockEntry] (shared with request_manager and sync_manager)
    • This queue is then regularly processed to be made available to the consensus object pools.
  • a xyzValidator message adds the validated object to a pool in eth2_processor
    • Attestations (unaggregated and aggregated) get collected into batches.
    • Once a threshold is exceeded or after a timeout, they get validated together using BatchCrypto.

Security concerns

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

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