Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create implementation of DHT using go-kademlia #408

Open
iand opened this issue Jul 11, 2023 · 1 comment
Open

Create implementation of DHT using go-kademlia #408

iand opened this issue Jul 11, 2023 · 1 comment
Labels
need/triage Needs initial labeling and prioritization

Comments

@iand
Copy link
Contributor

iand commented Jul 11, 2023 •
edited
Loading

ETA: 2023-08-31

go-kademila is a new modular Kademlia implementation designed to have predictable performance and resource utilization. We plan to refactor DHT responsibilities and behaviour between go-kademila, go-libp2p-kad-dht and boxo along the lines discussed in libp2p/go-libp2p-kad-dht#855

Motivations for refactoring the underlyiing DHT implementation are in probe-lab/roadmap#32

We need to implement a DHT type in boxo that configures KadDHT in go-libp2p-kad-dht wiith IPFS-specific parameters. We propose this lives in a new package: routing/dht. This new type will have minimal configuration options and sensible defaults and is designed to be simple to use for applications (such as Kubo) that operate using the standard public IPFS DHT network. Clients with different requirements should use KadDHT directly.
@iand iand added the need/triage Needs initial labeling and prioritization label Jul 11, 2023
@iand iand mentioned this issue Jul 11, 2023
Closed
@BigLep
Copy link
Contributor

BigLep commented Oct 19, 2023

@iand : is this task now done?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iand @BigLep