status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-15 07:57:42 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
Tanguy 36413c8f21
Bump libp2p for gossipsub improvements (#5229) 
* Bump libp2p

* Add bandwidthEstimate param

* Fix typo and type

* Add config for light client

* Fix unit

* Add debug prefix

---------

Co-authored-by: Jacek Sieka <jacek@status.im>
Co-authored-by: diegomrsantos <diegomrsantos@gmail.com>
Co-authored-by: Diego <diego@status.im>
2023-08-24 16:04:19 +02:00
..
eth2_discovery.nim
reduce nim-eth dependencies just for RNG (#5099)
2023-06-19 22:43:50 +00:00
eth2_network.nim
Bump libp2p for gossipsub improvements (#5229)
2023-08-24 16:04:19 +02:00
libp2p_json_serialization.nim
cleanup {.raises.} for writeValue (#5308)
2023-08-19 17:11:56 +02: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
Revert "Revert "correctly align genesis size (#5244)" (#5253)" (#5254)
2023-08-04 20:49:12 +00:00
network_metadata.nim
remove workaround for long-since-fixed Nim bug (#5219)
2023-07-31 22:20:09 +00:00
peer_pool.nim
bump chronos (#5039)
2023-06-08 13:42:19 +00:00
peer_scores.nim
harden req/resp peer scoring (#4966)
2023-05-19 15:01:27 +03:00
README.md
Reorg (5/5) (#2377)
2021-03-05 14:12:00 +01:00
topic_params.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00: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