Deprecating the DHT Public Key namespace
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
While I hope/suspect this is largely an IPFS issue https://github.com/ipfs/specs/issues/250, there may be users out there who are using the /pk DHT namespace as well as functions like dht.GetPublicKey().
If there are any users out there who would have use for the dht.GetPublicKey() function and are not prepared for it to be deprecated now is the time to speak up.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the related IPFS specs issue 250 and locating the dht.GetPublicKey() function and /pk DHT namespace in go-libp2p. Done would require a settled decision about whether these are still used and what deprecation work, if any, should follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100