status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/gossip_processing
History
Agnish Ghosh 250a80eb0c
add gossip validation for dc, and data column quarantine strategy (#6581) 
* add gossip validation for dc

* review 1

* rm callback

* review 2

* added custody columns as a global entity

* alpha 8

* few typosA
 		2024-10-22 05:19:34 +00:00
..
README.md automated consensus spec URL updating to v1.5.0-alpha.8 (#6617) 2024-10-09 08:37:35 +02:00
batch_validation.nim Use Pippenger multiplication for combining multiple sigs of same msg (#6484) 2024-08-16 23:42:46 +02:00
block_processor.nim Implement latest EIP-7685 `requestsHash` method (#6667) 2024-10-21 17:09:26 +02:00
eth2_processor.nim add Electra attester slashing gossip support (#6582) 2024-09-26 08:11:58 +02:00
gossip_validation.nim add gossip validation for dc, and data column quarantine strategy (#6581) 2024-10-22 05:19:34 +00:00
light_client_processor.nim extend light client protocol for Electra (#6375) 2024-06-26 19:02:03 +00:00
optimistic_processor.nim remove Bellatrix EL syncing support from light client (#6352) 2024-06-14 01:23:17 +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