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
Mapping for alternate hashes (hash index) #89
Comments
|
Excellent. Much needed in the long term. Thanks for documenting. |
|
|
|
This might also be useful for supporting other tools' public-key schemes |
|
Yes, the same index system could work for both, but I hope the address spaces are kept separate (similar to /ipfs/ versus /ipns/). |
8 tasks
|
I'm proposing to use something along the lines of https://github.com/dedis/cosi for this, together with a lightweight reputation system. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
btrask commentedDec 18, 2015
(Moved from ipfs/kubo#2098)
On Tuesday @jbenet was so kind as to spend a couple hours talking to me, where I got a chance to voice some of my concerns regarding ipfs/kubo#1953.
It seemed like one aspect Juan was amenable to was a way of looking up blocks (and possibly files) by hashes besides the primary hash (SHA-2 256) used by IPFS internally.
Features Juan wanted to see:
Features I wanted to see:
/ipls/[hash], for "link system")ipfs addreturning a file hash rather than a root block hash)We agreed that this system should not be built on top of IPNS. Hashes shouldn't rely on owners who have control of them, and don't need to be mutable.
It sounded like this was a fairly distant goal, but I figured we should at least start documenting our ideas.
Thanks again Juan for talking!
The text was updated successfully, but these errors were encountered: