nimbus-eth2/beacon_chain/networking
Jacek Sieka 0db1e768e4
don't write `node-metadata.json` on startup (#3515)
This file is not actually used / useful - should metadata persistence
support be added in the future, it needs to be done with a new file such
that downgrades, that have the TODO logic unimplemented, don't break.
2022-03-18 12:36:50 +01:00
..
README.md Reorg (5/5) (#2377) 2021-03-05 14:12:00 +01:00
eth2_discovery.nim Support for Gnosis Chain (#3415) 2022-02-25 10:22:44 +02:00
eth2_network.nim don't write `node-metadata.json` on startup (#3515) 2022-03-18 12:36:50 +01:00
faststreams_backend.nim add support for `ResourceUnavailable` p2p error (#3476) 2022-03-09 14:03:58 +00:00
libp2p_json_serialization.nim EH cleanup (#2455) 2021-03-26 07:52:01 +01:00
libp2p_streams_backend.nim add support for `ResourceUnavailable` p2p error (#3476) 2022-03-09 14:03:58 +00:00
network_metadata.nim update URL and document Nim bug blocking further genericizing cleanups (#3483) 2022-03-11 15:03:47 +00:00
peer_pool.nim EH cleanup (#2455) 2021-03-26 07:52:01 +01:00
peer_scores.nim Harden handling of unviable forks (#3312) 2022-01-26 13:20:08 +01: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