status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-06 11:44:45 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
Etan Kissling 86a265308a
filter out nil values when iterating peers (#6151) 
Iterating peers should only yield peers present in registry, otherwise
`nil` pointers are returned and depending on comparison function it will
break, see #6149.
2024-04-05 16:38:04 +02:00
..
eth2_discovery.nim
remove unnecessary exports in eth2_discovery (#5987)
2024-02-28 13:34:16 +00:00
eth2_network.nim
bump libp2p (#6148)
2024-03-27 15:53:02 +00:00
eth2_protocol_dsl.nim
simplify eth2_network error handling (#5765)
2024-01-19 21:05:52 +00:00
libp2p_json_serialization.nim
verify genesis_time more strictly (fixes #1667) (#5694)
2024-01-06 15:26:56 +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
rm built-in Goerli beacon chain support (#6057)
2024-04-03 23:25:36 +00:00
network_metadata.nim
rm built-in Goerli beacon chain support (#6057)
2024-04-03 23:25:36 +00:00
peer_pool.nim
filter out nil values when iterating peers (#6151)
2024-04-05 16:38:04 +02:00
peer_protocol.nim
add branch discovery module for supporting chain stall situation (#6125)
2024-03-24 08:41:47 +00:00
peer_scores.nim
add branch discovery module for supporting chain stall situation (#6125)
2024-03-24 08:41:47 +00:00
README.md
Reorg (5/5) (#2377)
2021-03-05 14:12:00 +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