status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-13 06:57:10 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/gossip_processing
History
Etan Kissling e4dacc30c4
fix validation of blob index against gossip topic (#5569) 
In `v1.4.0-alpha.0`, the blob index validation on gossip was changed to
use `compute_subnet_for_blob_sidecar` instead of having a separate topic
for each individual blob. We updated the spec reference in #5363 without
updating the code accordingly. Fixing this now, and also adding the new
`MAX_BLOBS_PER_BLOCK` check from `v1.4.0-beta.3` as it shares the theme.
2023-11-05 09:14:47 +01:00
..
batch_validation.nim
avoid Taskpool.spawn within {.async.} for Nim 2.0 (#5393)
2023-09-05 21:36:35 +02:00
block_processor.nim
automated consensus spec URL updating to v1.4.0-beta.3 (#5514)
2023-10-19 10:26:38 +00:00
eth2_processor.nim
avoid perpetually sending blobs to peers (#5563)
2023-11-04 20:36:12 +01:00
gossip_validation.nim
fix validation of blob index against gossip topic (#5569)
2023-11-05 09:14:47 +01:00
light_client_processor.nim
automated consensus spec URL updating to v1.4.0-beta.3 (#5514)
2023-10-19 10:26:38 +00:00
optimistic_processor.nim
remove {.raises: [Defect].} Nim 1.2 compatibility (#5352)
2023-08-25 11:29:07 +02:00
README.md
consensus-spec URL updates to v1.4.0-beta.3 (#5541)
2023-10-30 06:44:43 +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