GitLab

refactor: rename messageSender to peerMessageSender and added comments to clarify what peerMessageSender and messageManager do

refactor: extract messaging components from IpfsDHT into its own struct. create a new struct that manages sending DHT messages that can be used independently from the DHT.

reorder startup events so that everything but the refresh manager starts before we add already connected peers to our routing table

testing: add test-specific option to force processing of Host address changes even when AutoRefresh is disabled

* reduce churn

This reverts commit c9851849.

* fix: fixLowPeers now runs periodically
Co-authored-by: 刘林欣 <llx@ipfsmain.cn>

This reverts commit df4f28c3.

Ongoing work is being done in feat/dht-hardening-0.7 and this change isn't quite ready.

Anything else is easy to game. This way, we remain connected to the core peers
and slightly prefer all others.

Pruning doesn't really matter as we'll just reconnect. The only concern is that
this will lock in 40 connections. However, that's nothing for libp2p anyways.
and the DHT will create that many connections _just_ for a single query.

* Peer Diversity in the DHT

* method for getting bootstrap peers and double the usefulness interval

And tag useful peers in higher buckets

That way, we never disconnect from the core of the network.

We don't protect our closest peers as:

* We'll reconnect to them frequently when we query for ourself.
* We use the core nodes most frequently.

* rt refresh refactor

* Bootstrap when RT is empty and optimize allocations.
Co-authored-by: Steven Allen <steven@stebalien.com>

They've told us better ones via identify.

These are all critical paths so we should try to do as little work as possible.