mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-12 22:46:59 +00:00

History

send attestations and exit messages on fork-appropriate topic (#2773 )

* send attestations and exit messages on fork-appropriate topic

* document why use wall clock over attestation slot

* centralize some fork-topic-picking-logic in eth2_network

* pick up new test in summary

* allow specified GetTimeFn for testing purposes

* add GenesisTime and use it in eth2_network

* replace GetTimeFn and GenesisTime with GetBeaconTimeFn

2021-08-19 10:45:31 +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

send attestations and exit messages on fork-appropriate topic (#2773 )

2021-08-19 10:45:31 +00: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

disentangle eth2 types from the ssz library (#2785 )

2021-08-18 20:57:58 +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