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
tersec 2b2846b468
implement forked merge state/block support (#2890) 
* implement forked state/block support

* merge support for containsOrphan; import cleanup; 80-column lines

* add merge block header operations and slot sanity fixture

* add epoch state transition tests; implement is_valid_gas_limit(), is_merge_block(), is_execution_enabled(), and compute_timestamp_at_slot()

* implement process_execution_payload() and add merge deposit operations tests

* add merge block sanity tests

* add merge case to syncCommitteeParticipants

* v1.1.0-beta.5 updates

* reduce getTestStates-based memory usage; don't try to REST-serialize ExecutionPayload transactions without underlying support

* add execution payload tests; switch var to let in tests/official/
2021-09-27 14:22:58 +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
implement forked merge state/block support (#2890)
2021-09-27 14:22:58 +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
Clarify why 'eth1Network' is an Option type
2021-09-08 15:47:48 +03: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