status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-08 20:54:33 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
Jacek Sieka 3f525acb87
chronos: bump (#5684) 
This PR causes a few new warnings to appear - these are harmless but
will need addressing separately as they span several libraries.

* new asyncraises syntax
* asyncraises support in several modules
* `sink` usage reduces spurious copying
* `?` compatiblity for `async` + `results`
* remove `-d:chronosStrictException` (obsolete)
2024-01-05 10:08:38 +01:00
..
eth2_discovery.nim
bump nim-eth to remove ValidIpAddress and replace with IpAddress (#5587)
2023-11-10 16:58:48 +01:00
eth2_network.nim
chronos: bump (#5684)
2024-01-05 10:08:38 +01:00
libp2p_json_serialization.nim
remove {.raises: [Defect].} Nim 1.2 compatibility (#5352)
2023-08-25 11:29:07 +02:00
network_metadata_downloads.nim
Version 23.9.1
2023-09-25 21:24:25 +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
network_metadata.nim
bump goerli to 6522ac6684693740cd4ddcc2a0662e03702aa4a1 (#5687)
2024-01-02 22:39:55 +01:00
peer_pool.nim
BN+LC+SN: Fix cancellation deprecate warnings. (#5455)
2023-09-22 11:06:27 +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