status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-24 21:40:03 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
Etan Kissling 52ba4f7999
rename light client config parameters (#3740) 
For consistency with other options, use a common prefix for light client
data configuration options.

* `--serve-light-client-data` --> `--light-client-data-serve`
* `--import-light-client-data` --> `--light-client-data-import-mode`

No deprecation of the old identifiers as they were only sparingly used
and all usage can be easily updated without interferance.
2022-06-14 12:03:39 +03:00
..
eth2_discovery.nim
add light client (standalone) (#3653)
2022-05-31 12:45:37 +02:00
eth2_network.nim
rename light client config parameters (#3740)
2022-06-14 12:03:39 +03:00
libp2p_json_serialization.nim
enable styleCheck:usages (#3573)
2022-04-08 16:22:49 +00:00
network_metadata.nim
rename light client config parameters (#3740)
2022-06-14 12:03:39 +03:00
peer_pool.nim
add light client (standalone) (#3653)
2022-05-31 12:45:37 +02:00
peer_scores.nim
NoMonitor and removed clock check for SyncManager. (#3420)
2022-04-14 15:17:44 +02:00
README.md
Reorg (5/5) (#2377)
2021-03-05 14:12:00 +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