Skip to content

docs: clarify FIND_NODE response for DHT-client nodes #644

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

Open
achingbrain wants to merge 3 commits into
base: master
Choose a base branch
from
Open

docs: clarify FIND_NODE response for DHT-client nodes #644

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5f58325
docs: clarify FIND_NODE response for DHT-client nodes
achingbrain Nov 21, 2024
c703141
chore: missed a word
achingbrain Nov 21, 2024
fd86276
chore: clarify
achingbrain Nov 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion kad-dht/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -490,7 +490,9 @@ These are the requirements for each `MessageType`:

* `FIND_NODE`: In the request `key` must be set to the binary `PeerId` of the
node to be found. In the response `closerPeers` is set to the `k` closest
`Peer`s.
`Peer`s. Each closer peer will be a DHT server, unless `key` is an exact match
for a peer known to the node, in which case the closer peers will include the
matching peer, even if it is not a DHT server.

* `GET_VALUE`: In the request `key` is an unstructured array of bytes. `record`
is set to the value for the given key (if found in the datastore) and
Expand Down