Kad PUT_VALUE response deviating from the spec
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.6k
- Forks
- 1.3k
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 19
Description
Description
The spec says that a PUT_VALUE response message should have key and record fields set, however this implementaion does the following instead:
Motivation
It should follow the spec
Current Implementation
Uses key and value
Are you planning to do it yourself in a pull request?
Maybe
Contributor guide
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 in protocols/kad/src/protocol.rs at the linked lines and compare the PUT_VALUE response construction with the kad-dht RPC message specification. Update the response so its fields match the spec, using key and record rather than key and value; done means the implementation conforms to the cited response requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100