Skip to content

Commit

Permalink
kad-dht/README: Do not require storing provider addresses
Browse files Browse the repository at this point in the history
  • Loading branch information
@mxinden
mxinden committed Jun 25, 2021
1 parent 3e13846 commit 6ec65b5
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions kad-dht/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -249,9 +249,11 @@ key, the DHT finds the closest peers to the key using the `FIND_NODE` RPC (see
[peer routing section](#peer-routing)), and then sends an `ADD_PROVIDER` RPC with
its own `PeerInfo` to each of these peers.

Each peer that receives the `ADD_PROVIDER` RPC should validate that the
received `PeerInfo` matches the sender's `peerID`, and if it does, that peer
must store the `PeerInfo` in its datastore.
Each peer that receives the `ADD_PROVIDER` RPC should validate that the received
`PeerInfo` matches the sender's `peerID`, and if it does, that peer should store
the `PeerInfo` in its datastore. Implementations may choose to not store the
addresses of the providing peer e.g. to reduce the amount of required storage or
to prevent storing potentially outdated address information.

#### Content provider discovery

Expand Down

0 comments on commit 6ec65b5

Please sign in to comment.