nimbus-eth2/beacon_chain/networking
Jacek Sieka 138c40161d
avoid unnecessary recompression in block protocol (#3598)
Blocks can be sent straight from compressed data sources

Co-authored-by: Etan Kissling <etan@status.im>
2022-05-05 11:00:02 +00:00
..
README.md Reorg (5/5) (#2377) 2021-03-05 14:12:00 +01:00
eth2_discovery.nim remove TaintedString (#3546) 2022-03-24 21:44:34 +00:00
eth2_network.nim avoid unnecessary recompression in block protocol (#3598) 2022-05-05 11:00:02 +00:00
faststreams_backend.nim use MAX_CHUNK_SIZE_BELLATRIX for signed Bellatrix blocks (#3613) 2022-05-05 05:45:35 +00:00
libp2p_json_serialization.nim enable `styleCheck:usages` (#3573) 2022-04-08 16:22:49 +00:00
libp2p_streams_backend.nim use MAX_CHUNK_SIZE_BELLATRIX for signed Bellatrix blocks (#3613) 2022-05-05 05:45:35 +00:00
network_metadata.nim post-merge Bellatrix block proposals (#3570) 2022-04-14 20:15:34 +00:00
peer_pool.nim EH cleanup (#2455) 2021-03-26 07:52:01 +01:00
peer_scores.nim NoMonitor and removed clock check for SyncManager. (#3420) 2022-04-14 15:17:44 +02: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