nimbus-eth2/beacon_chain/networking
Zahary Karadjov 05fb7ffff0
Don't require getopt to be installed by brew on macOS for Nix users
Other changes:

* Add/Update copyright banners
* Add post-review comment for https://github.com/status-im/nimbus-eth2/pull/5719
2024-01-13 12:37:41 +02:00
..
README.md Reorg (5/5) (#2377) 2021-03-05 14:12:00 +01:00
eth2_discovery.nim Avoid global in p2p macro (fixes #4578) (#5719) 2024-01-13 11:54:24 +02:00
eth2_network.nim Don't require getopt to be installed by brew on macOS for Nix users 2024-01-13 12:37:41 +02:00
eth2_protocol_dsl.nim Avoid global in p2p macro (fixes #4578) (#5719) 2024-01-13 11:54:24 +02:00
libp2p_json_serialization.nim verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +01:00
network_metadata.nim bump `gnosis-chain-configs` to `ff5fbe9aecbf28df9beedb662920eeee537629b0` (#5725) 2024-01-12 11:31:07 +01:00
network_metadata_downloads.nim add missing `std/` prefix to more imports (#5696) 2024-01-06 07:18:28 +01: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 load Goerli metadata from `goerli` repo (#5680) 2024-01-02 16:15:44 +01:00
peer_pool.nim verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +01:00
peer_protocol.nim Avoid global in p2p macro (fixes #4578) (#5719) 2024-01-13 11:54:24 +02:00
peer_scores.nim verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +01:00
topic_params.nim verify `genesis_time` more strictly (fixes #1667) (#5694) 2024-01-06 15:26:56 +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