status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-01-09 13:56:23 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
Jacek Sieka a086cf01ac
altair fork handling cleanups (#3050) 
* fix stack overflow crash in REST/debug/getStateV2
* introduce `ForkyXxx` for generic type matching of `Xxx` across
branches (SomeHashedBeaconState -> ForkyHashedBeaconState et al) -
`Some` is already used for other types of type classes
* consolidate function naming in BeaconChainDB, use some generics
* import `forks.nim` from other spec modules and move `Forked*` helpers
around to resolve circular imports
* remove `ForkedBeaconState`, use `ForkedHashedBeaconState` throughout
(less data shuffling between the types)
* fix several cases of states being stored on stack in tests, causing
random failures on some platforms
* remove reading json support from ncli - this should be ported to the
rest json reading instead (doesn't currently work because stack sizes)
2021-11-05 08:34:34 +01:00
..
eth2_discovery.nim
log doppelganger attestation signature; rm withState.HashedBeaconState uses (#2608)
2021-05-28 15:51:15 +03:00
eth2_network.nim
altair fork handling cleanups (#3050)
2021-11-05 08:34:34 +01:00
faststreams_backend.nim
Implement split preset/config support (#2710)
2021-07-12 15:01:38 +02:00
libp2p_json_serialization.nim
EH cleanup (#2455)
2021-03-26 07:52:01 +01:00
libp2p_streams_backend.nim
Implement split preset/config support (#2710)
2021-07-12 15:01:38 +02:00
network_metadata.nim
test fixture cleanups (#2976)
2021-10-12 13:36:52 +02: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