10215dbc14
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. |
||
---|---|---|
.. | ||
README.md | ||
eth2_discovery.nim | ||
eth2_network.nim | ||
libp2p_json_serialization.nim | ||
network_metadata.nim | ||
peer_pool.nim | ||
peer_scores.nim | ||
topic_params.nim |
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