This repository has been archived by the owner on May 12, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea is to make a network where nodes can add values to the DHT (and not store them locally, a value should be stored in the closest node to its key) and others who have the keys (which for me are
sha2-256 multihash
) can retrieve these values.So to get these nodes to be in the same network without having to hardcode the addresses etc. I found the pubsub pattern (the code im using is the
pubsub
example in theipfs-camp-2019
) that can give me this, and i found a DHT already defined there for routing.This example uses
Provide()
to tell nodes that it has a certainCID
and peers :CID
of the value i want to storeCID
bydht.GetClosestPeers()
CID
and the value (using thechat
example)key:value
to the storage, it executesdht.Provide()
to announce that it has that entrydht.FindProviders()
to find a peer having that, and it establishes a connection with it to retrieve the value from its local storage.