status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
tersec a4f4a35845
Revert "initial Electra support skeleton" (#5955) 
* Revert "initial Electra support skeleton (#5946)"

This reverts commit d09bf3b587.

* Update test_signing_node.nim
 		2024-02-25 19:42:44 +00:00
..
README.md
…
eth2_discovery.nim Avoid global in p2p macro (fixes #4578) (#5719) 2024-01-13 11:54:24 +02:00
eth2_network.nim Revert "initial Electra support skeleton" (#5955) 2024-02-25 19:42:44 +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.nim Revert "initial Electra support skeleton" (#5955) 2024-02-25 19:42:44 +00: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 unrevert more of https://github.com/status-im/nimbus-eth2/pull/5765 (#5834) 2024-01-29 08:35:16 +01:00
peer_protocol.nim automated consensus spec URL updating to v1.4.0-beta.7 (#5942) 2024-02-21 19:44:48 +00: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