nimbus-eth2/beacon_chain/networking
Jacek Sieka 4d74c742da
move ENRForkID into `spec` (#2538)
* move ENRForkID into `spec`

also get rid of strformat in topic formation and fix some case
discrepancies

* also move `Eth2Metadata`
2021-05-04 17:28:48 +02:00
..
README.md Reorg (5/5) (#2377) 2021-03-05 14:12:00 +01:00
eth2_discovery.nim EH cleanup (#2455) 2021-03-26 07:52:01 +01:00
eth2_network.nim move ENRForkID into `spec` (#2538) 2021-05-04 17:28:48 +02:00
faststreams_backend.nim Reorg (5/5) (#2377) 2021-03-05 14:12:00 +01:00
libp2p_json_serialization.nim EH cleanup (#2455) 2021-03-26 07:52:01 +01:00
libp2p_streams_backend.nim Reorg (5/5) (#2377) 2021-03-05 14:12:00 +01:00
network_metadata.nim json cleanups (#2456) 2021-03-26 15:11:06 +01:00
peer_pool.nim EH cleanup (#2455) 2021-03-26 07:52:01 +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