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

kad-dht/README: Document key on Message during PUT_VALUE #373

Merged
merged 1 commit into from
Nov 16, 2021
Merged

kad-dht/README: Document key on Message during PUT_VALUE #373

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
9 changes: 5 additions & 4 deletions kad-dht/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

| Lifecycle Stage | Maturity | Status | Latest Revision |
|-----------------|----------------|--------|-----------------|
| 3A | Recommendation | Active | r0, 2021-05-07 |
| 3A | Recommendation | Active | r1, 2021-10-30 |

Authors: [@raulk], [@jhiesey], [@mxinden]

Expand Down Expand Up @@ -404,9 +404,10 @@ These are the requirements for each `MessageType`:
is set to the value for the given key (if found in the datastore) and
`closerPeers` is set to the `k` closest peers.

* `PUT_VALUE`: In the request `key` is an unstructured array of bytes. The
target node validates `record`, and if it is valid, it stores it in the
datastore.
* `PUT_VALUE`: In the request `record` is set to the record to be stored and `key`
on `Message` is set to equal `key` of the `Record`. The target node validates
`record`, and if it is valid, it stores it in the datastore and as a response
echoes the request.

* `GET_PROVIDERS`: In the request `key` is set to a CID. The target node
returns the closest known `providerPeers` (if any) and the `k` closest known
Expand Down