Closed
Description
Description
Mirroring libp2p/go-libp2p-kad-dht#254, it would be great if long-lasting peers were persisted and used for bootstrapping later.
Motivation
Using bootstrap nodes outside of the default ones improves network resiliency, and potentially improves initial connections times when the new bootstrap nodes are closer than they otherwise would be.
Requirements
- Save the longest lasting peer(s) from each k-bucket where it can be re-used for bootstrapping.
Open questions
- Which k-buckets are considered, and how many peers are picked from each bucket?
- Should latency be factored into picking future bootstrap nodes? If so, how?
- Other open questions mentioned at Saving previously seen nodes for later bootstrapping ipfs/kubo#3926 and Persist routing table go-libp2p-kad-dht#254.
Are you planning to do it yourself in a pull request?
No
Metadata
Metadata
Assignees
Labels
No labels