fc9bc1da3a
In split view situation, the canonical chain may only be served by a tiny amount of peers, and branches may span long durations. Minority branches may still have a large weight from attestations and should be discovered. To assist with that, add a branch discovery module that assists in such a situation by specifically targeting peers with unknown histories and downloading from them, in addition to sync manager work which handles popular branches. |
||
|---|---|---|
| .. | ||
| README.md | ||
| eth2_discovery.nim | ||
| eth2_network.nim | ||
| eth2_protocol_dsl.nim | ||
| libp2p_json_serialization.nim | ||
| network_metadata.nim | ||
| network_metadata_downloads.nim | ||
| network_metadata_gnosis.S | ||
| network_metadata_mainnet.S | ||
| peer_pool.nim | ||
| peer_protocol.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