status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-09 22:06:21 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
tersec e78d12beb9
support GOSSIP_MAX_SIZE_MERGE blocks; prevent fork choice stutter via aggregate attestations (#3230) 
* support GOSSIP_MAX_SIZE_MERGE-sized blocks; prevent fork choice clock stutter via aggregate attestations

* relay max gossip size to libp2p, use tight uncompressed bounds for fixed-size messages

* Update beacon_chain/networking/eth2_network.nim

Co-authored-by: Jacek Sieka <jacek@status.im>

* Update beacon_chain/networking/eth2_network.nim

Co-authored-by: Jacek Sieka <jacek@status.im>

Co-authored-by: Jacek Sieka <jacek@status.im>
2022-01-03 16:20:15 +00:00
..
eth2_discovery.nim
log doppelganger attestation signature; rm withState.HashedBeaconState uses (#2608)
2021-05-28 15:51:15 +03:00
eth2_network.nim
support GOSSIP_MAX_SIZE_MERGE blocks; prevent fork choice stutter via aggregate attestations (#3230)
2022-01-03 16:20:15 +00:00
faststreams_backend.nim
add copyright header to streams backends (#3177)
2021-12-10 02:28:09 +00:00
libp2p_json_serialization.nim
EH cleanup (#2455)
2021-03-26 07:52:01 +01:00
libp2p_streams_backend.nim
add copyright header to streams backends (#3177)
2021-12-10 02:28:09 +00:00
network_metadata.nim
fix typo (snapshop -> snapshot) (#3192)
2021-12-14 15:44:34 +00:00
peer_pool.nim
EH cleanup (#2455)
2021-03-26 07:52:01 +01:00
README.md
Reorg (5/5) (#2377)
2021-03-05 14:12:00 +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