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 7e276937dc
make LC data fork aware (#4493) 
In a future fork, light client data will be extended with execution info
to support more use cases. To anticipate such an upgrade, introduce
`Forky` and `Forked` types, and ready the database schema.
Because the mapping of sync committee periods to fork versions is not
necessarily unique (fork schedule not in sync with period boundaries),
an additional column is added to `period` -> `LightClientUpdate` table.
 		2023-01-12 18:11:38 +01:00
..
README.md a few consensus spec ref URL updates (#4483) 2023-01-10 16:14:17 +00:00
batch_validation.nim spec: Option -> Opt (#4488) 2023-01-11 12:29:21 +00:00
block_processor.nim Wire up engine_newPayloadV3 (#4482) 2023-01-11 18:21:19 +00:00
eth2_processor.nim make LC data fork aware (#4493) 2023-01-12 18:11:38 +01:00
gossip_validation.nim make LC data fork aware (#4493) 2023-01-12 18:11:38 +01:00
light_client_processor.nim make LC data fork aware (#4493) 2023-01-12 18:11:38 +01:00
optimistic_processor.nim rm optimistic candidate block check from LC (#4131) 2022-09-17 00:42:19 +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