nimbus-eth2/beacon_chain/networking
Etan Kissling 10215dbc14
make deployment phase configurable (#4231)
Allow config of deployment phase via config instead of attempting to
derive from genesis content (when running relevant testnets), so that
we don't have to keep maintaining the list inside the binary.
2022-10-12 22:58:36 +00:00
..
README.md Reorg (5/5) (#2377) 2021-03-05 14:12:00 +01:00
eth2_discovery.nim compatibility with Nim 1.4+ (#3888) 2022-07-29 10:53:42 +00:00
eth2_network.nim add beaconcha.in mainnet relay overview to guide (#4217) 2022-10-04 19:45:06 +03:00
libp2p_json_serialization.nim compatibility with Nim 1.4+ (#3888) 2022-07-29 10:53:42 +00:00
network_metadata.nim make deployment phase configurable (#4231) 2022-10-12 22:58:36 +00:00
peer_pool.nim compatibility with Nim 1.4+ (#3888) 2022-07-29 10:53:42 +00:00
peer_scores.nim update `PeerScore` comments for non-blocks (#4191) 2022-09-28 18:56:04 +00:00
topic_params.nim reduce LC optsync latency (#4002) 2022-08-25 03:53:59 +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