status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-24 21:40:03 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
henridf d7316ac863
Wire up blob fetching with request manager (#4527) 
* Wire up blob fetching and request manager

* Update beacon_chain/sync/request_manager.nim

Co-authored-by: tersec <tersec@users.noreply.github.com>

* Review feedback: remove redundant RequestManager field.

* Fix syntax

* Improve blob fetching logic

* fix previous commit

* rman.isBlobsTime(): Remove spurious parameter

* Review feedback

* expressionify an if

---------

Co-authored-by: tersec <tersec@users.noreply.github.com>
2023-02-01 00:25:08 +01:00
..
eth2_discovery.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00
eth2_network.nim
Wire up blob fetching with request manager (#4527)
2023-02-01 00:25:08 +01:00
libp2p_json_serialization.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00
network_metadata.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00
peer_pool.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00
peer_scores.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00
README.md
Reorg (5/5) (#2377)
2021-03-05 14:12:00 +01:00
topic_params.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00:00

README.md

Networking

This folders hold a collection of modules to:

  • configure the Eth2 P2P network
  • discover, connect, and maintain quality Eth2 peers

Data received is handed other to the ../gossip_processing modules for validation.

Security concerns

  • Collusion: part of the peer selection must be kept random. This avoids peers bringing all their friends and colluding against a beacon node.
  • Denial-of-service: The beacon node must provide ways to handle burst of data that may come:
    • from malicious nodes trying to DOS us
    • from long periods of non-finality, creating lots of forks, attestations, forks