History

Etan Kissling 8064f5bcce explicitly mention which `Success` enum to use (#5309 ) In Nim 2.0 it can no longer infer that we mean `ResponseCode.Success` inside `eth2_network`. Explicitly refer to that type to work around.		2023-08-17 18:33:35 +00:00
..
README.md	Reorg (5/5) (#2377 )	2021-03-05 14:12:00 +01:00
eth2_discovery.nim	reduce `nim-eth` dependencies just for RNG (#5099 )	2023-06-19 22:43:50 +00:00
eth2_network.nim	explicitly mention which `Success` enum to use (#5309 )	2023-08-17 18:33:35 +00:00
libp2p_json_serialization.nim	remove Nim 1.2-compatible `push raise`s and update copyright notice years (#4528 )	2023-01-20 14:14:37 +00:00
network_metadata.nim	remove workaround for long-since-fixed Nim bug (#5219 )	2023-07-31 22:20:09 +00:00
network_metadata_gnosis.S	Revert "Revert "correctly align genesis size (#5244 )" (#5253 )" (#5254 )	2023-08-04 20:49:12 +00:00
network_metadata_mainnet.S	Revert "Revert "correctly align genesis size (#5244 )" (#5253 )" (#5254 )	2023-08-04 20:49:12 +00:00
peer_pool.nim	bump chronos (#5039 )	2023-06-08 13:42:19 +00:00
peer_scores.nim	harden req/resp peer scoring (#4966 )	2023-05-19 15:01:27 +03:00
topic_params.nim	remove Nim 1.2-compatible `push raise`s 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