status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-09 21:24:01 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/gossip_processing
History
Jacek Sieka 83f9745df1
restore doppelganger check on connectivity loss (#4616) 
* restore doppelganger check on connectivity loss

https://github.com/status-im/nimbus-eth2/pull/4398 introduced a
regression in functionality where doppelganger detection would not be
rerun during connectivity loss. This PR reintroduces this check and
makes some adjustments to the implementation to simplify the code flow
for both BN and VC.

* track when check was last performed for each validator (to deal with
late-added validators)
* track when we performed a doppel-detectable activity (attesting) so as
to avoid false positives
* remove nodeStart special case (this should be treated the same as
adding a validator dynamically just after startup)

* allow sync committee duties in doppelganger period

* don't trigger doppelganger when registering duties

* fix crash when expected index response is missing

* fix missing slashingSafe propagation
2023-02-20 13:28:56 +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
don't fcU on blocks for which block processor received no newPayload reply (#4623)
2023-02-14 21:41:49 +01:00
eth2_processor.nim
restore doppelganger check on connectivity loss (#4616)
2023-02-20 13:28:56 +02:00
gossip_validation.nim
refactor batch validation not to require genesis_validators_root each time (#4640)
2023-02-20 09:26:22 +01:00
light_client_processor.nim
avoid sending redundant LC finality updates (#4546)
2023-01-24 17:44:55 +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
automated v1.3.0-rc.1 to v1.3.0-rc.2 consensus spec URL updates (#4568)
2023-01-31 00:26:57 +01: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