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
Etan Kissling 9fc870777c
remove Bellatrix EL syncing support from light client (#6352) 
Bellatrix light client data does not contain the EL block hash, so we
had to follow blocks gossip to learn the EL `block_hash` of such blocks.
Now that Bellatrix is obsolete, we can simplify EL syncing logic under
light client scenarios. Bellatrix light client data can still be used
to advance the light client sync itself, but will no longer result in
`engine_forkchoiceUpdated` calls until the sync reaches Capella. This
also frees up some memory as we no longer have to retain blocks.
 		2024-06-14 01:23:17 +00:00
..
README.md some consensus spec v1.4.0 spec URL updates (#6208) 2024-04-17 05:51:16 +02:00
batch_validation.nim add some support for electra aggregated attestations (#6283) 2024-05-14 06:12:35 +02:00
block_processor.nim bump nim-kzg4844 for gcc-14 compatibility (#6342) 2024-06-14 00:46:03 +00:00
eth2_processor.nim VC/NIMBUS-BN validators protection. (#6329) 2024-06-11 19:38:16 +00:00
gossip_validation.nim bump nim-kzg4844 for gcc-14 compatibility (#6342) 2024-06-14 00:46:03 +00:00
light_client_processor.nim raises for gossip (#5808) 2024-01-22 17:34:54 +01: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