libp2p / libp2p/developer-meetings
[Protocol Design] How to create a fully private DHT
Open
@Stebalien is already working on this.
Since Jul 2, 2018.
deep-dive
transfered-to-sched
- Dominant language
- No language data
- Stars
- 7
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Figuring out how to create private DHT
Name: @Stebalien
Length (choose one): 1 hour meeting
Title (~1-7 words): Privacy Preserving Routing
Abstract (1 sentence up to a couple paragraphs, as you prefer):
In this session, we'll explore ways to improve privacy in IPFS with a focus on the DHT. For a longer writeup, see: https://github.com/ipfs/notes/issues/291#issuecomment-396003860.
This should allow:
- Private content routing. It should no longer be possible to enumerate all the content stored on IPFS simply by spinning up a bunch of DHT nodes. Bonus: zero knowledge bitswap queries.
- Private peer routing. Finding a peer will require knowing the peer's ID. To make this useful, peers will need a public ephemeral ID and a permanent ID. The ephemeral ID will be used for content routing, the DHT, etc. while the permanent ID will be used for access control lists, etc.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.