status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-12 22:46:59 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/beacon_chain/networking
History
Etan Kissling d8a7f0df81
update Deneb for blob sidecar inclusion proofs (#5565) 
`BlobSidecar` is no longer signed, instead use Merkle proof to link
blobs with block.

- https://github.com/ethereum/consensus-specs/pull/3531

Associated beacon-API / builder-specs still TBD; minimal changes done
to compile in similar style to previous spec, but not standardized yet.

- https://github.com/ethereum/beacon-APIs/pull/369
- https://github.com/ethereum/builder-specs/pull/90
2023-11-06 07:48:43 +01:00
..
eth2_discovery.nim
fix mainnet bootstrap node comment parsing; fix nimbus guide grammar (#5486)
2023-10-06 19:26:30 +00:00
eth2_network.nim
update Deneb for blob sidecar inclusion proofs (#5565)
2023-11-06 07:48:43 +01:00
libp2p_json_serialization.nim
remove {.raises: [Defect].} Nim 1.2 compatibility (#5352)
2023-08-25 11:29:07 +02:00
network_metadata_downloads.nim
Version 23.9.1
2023-09-25 21:24:25 +01:00
network_metadata_gnosis.S
Revert "Revert "correctly align genesis size (#5244)" (#5253)" (#5254)
2023-08-04 20:49:12 +00:00
network_metadata_mainnet.S
Revert "Revert "correctly align genesis size (#5244)" (#5253)" (#5254)
2023-08-04 20:49:12 +00:00
network_metadata.nim
rm unused code (#5538)
2023-11-01 05:53:09 +01:00
peer_pool.nim
BN+LC+SN: Fix cancellation deprecate warnings. (#5455)
2023-09-22 11:06:27 +00:00
peer_scores.nim
harden req/resp peer scoring (#4966)
2023-05-19 15:01:27 +03:00
README.md
…
topic_params.nim
remove Nim 1.2-compatible push raises and update copyright notice years (#4528)
2023-01-20 14:14:37 +00: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