status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-08 20:54:33 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
zah c29aa9d846
Support for Gnosis Chain (#3415) 
* Support for Gnosis Chain

`make gnosis-chain-build` will build the Nimbus gnosis chain binary,
stored in `build/nimbus_beacon_node_for_gnosis_chain`.

`make gnosis-chain` will connect to the network.

Other changes:

* Restore compilation with -d:has_genesis_detection
* Removed Makefile target related to testnet0 and testnet1
* Added more debug logging for failed peer handshakes
* Report misconfigured builds which try to embed network metadata
that is incompatible with the currently selected const preset.
* Don't bundle network metadata in minimal builds, as they are not compatible
2022-02-25 10:22:44 +02:00
..
eth2_discovery.nim
Support for Gnosis Chain (#3415)
2022-02-25 10:22:44 +02:00
eth2_network.nim
rename no{R=>r}eturn, no{I=>i}init, short{l=>L}og, E{T=>t}h2Node, Beacon{c=>C}hainDB (#3403)
2022-02-16 23:24:44 +01: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
Support for Gnosis Chain (#3415)
2022-02-25 10:22:44 +02:00
network_metadata.nim
Support for Gnosis Chain (#3415)
2022-02-25 10:22:44 +02:00
peer_pool.nim
EH cleanup (#2455)
2021-03-26 07:52:01 +01:00
peer_scores.nim
Harden handling of unviable forks (#3312)
2022-01-26 13:20:08 +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