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.

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

Communicate with network indexers for content routing using reader privacy with double hashing #9455

Open
BigLep opened this issue Dec 5, 2022 · 1 comment

Comments

@BigLep
Copy link
Contributor

BigLep commented Dec 5, 2022

Done Criteria

Content routing calls like findProviders to Network Indexers like cid.contact preserve reader privacy with double hashing. Using double hashing is the implicit default.

Why Important

Move IPFS' privacy story forward so that centralized endpoints like network indexers are not even able to know "who is contacting what". This is about getting to a system where we don't have to trust network indexers to respect a client's privacy.

Notes

  1. There is a lot still be designed here. This is the Kubo tracking issue so we can link to other work.
  2. This is a followup to Add implicit HTTP delegated router for cid.contact network indexer #9454
  3. Related docs:
@BigLep
Copy link
Contributor Author

BigLep commented Aug 4, 2023

There is still open spec work for this (ipfs/specs#421 ) and then the client implementation needs to land in boxo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant