[Protocol Design] How to create a fully private DHT

[ghost]

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: ipfs/notes#291 (comment).

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.

[daviddias]

Intended format described here ipfs-inactive/conf#43

[daviddias]

@Stebalien wanna lead this one. Basing my suggestion on ipfs/notes#291

[Stebalien]

Ah. A privacy preserving DHT? Sure.

[daviddias]

Please drop your notes to https://github.com/libp2p/developer-meetings/tree/master/notes