status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-20 11:29:51 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
Agnish Ghosh 1ebba1fac4
add: metadata-v3 for custody subnet count (#6486) 
* init: add metadatav3, save progress

* fix import issues

* fix spec version

* fix: metadata_v2 to return altair.MetaData

* update metata function backward compatible now
2024-08-12 21:27:37 +05:30
..
eth2_discovery.nim
added enr struct
2024-07-15 13:11:09 +05:30
eth2_network.nim
add: metadata-v3 for custody subnet count (#6486)
2024-08-12 21:27:37 +05:30
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
rank peers by their score instead of their memory address (#6149)
2024-04-10 14:09:37 +02:00
peer_protocol.nim
add: metadata-v3 for custody subnet count (#6486)
2024-08-12 21:27:37 +05:30
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