status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-11 14:06:47 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
Agnish Ghosh c728d8754c
custody subnet count decoding during discovery (#6777) 
* renamed eip7594_helpers to peerdas_helpers, added csc subnet decoding during discovery

* added link
2024-12-20 11:23:46 +01:00
..
eth2_agents.nim
fix some UnusedImport warnings (#6448)
2024-07-25 08:49:26 +00:00
eth2_discovery.nim
custody subnet count decoding during discovery (#6777)
2024-12-20 11:23:46 +01:00
eth2_network.nim
custody subnet count decoding during discovery (#6777)
2024-12-20 11:23:46 +01:00
eth2_protocol_dsl.nim
network: remove unusede p2p macro stuff (#6700)
2024-11-01 16:40:13 +01: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
bump sepolia for new bootnodes (#6421)
2024-07-11 07:13:37 +02:00
network_metadata.nim
Support reading bootstrap_nodes.yaml (#6751)
2024-12-09 13:38:56 +00:00
peer_pool.nim
rank peers by their score instead of their memory address (#6149)
2024-04-10 14:09:37 +02:00
peer_protocol.nim
getMetaData_v3 (#6739)
2024-11-30 16:53:02 +01:00
peer_scores.nim
add branch discovery module for supporting chain stall situation (#6125)
2024-03-24 08:41:47 +00:00
README.md
Typos Documentation in README.md Files (#6771)
2024-12-18 09:24:13 +00:00
topic_params.nim
verify genesis_time more strictly (fixes #1667) (#5694)
2024-01-06 15:26:56 +01:00

README.md

Networking

These folders hold a collection of modules to:

  • configure the Eth2 P2P network
  • discover, connect, and maintain quality Eth2 peers

Data received is handed over 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