3 ms·
Just use a public key as your address, and make signed pointers to the actual content. That's how people have been solving the update problem for ages. Naming
by bawolff 4y ago
Just use a public key as your address, and make signed pointers to the actual content. That's how people have been solving the update problem for ages.
Naming things continues to be one of the hard problems in computer science.
- toomim 4y agoThen it's no longer content-addressing. It's now "public key plus a signed pointer referencing a name-that-has-yet-to-be-specified" addressing. I think that's a fine road to go down for addressing data, but it's not content addressing.
- bawolff 4y agoWhy not? If you include the public key with the signed pointer, then you can define a "hash" function that returns just the pubkey (yes with collisions, but not in a way that matters) and it is content-addressing. After all, you are literally addressing by content in this scheme. What is actually the difference in any way that matters? What property does content addressing have that this doesn't.
- theGnuMe 4y agoI mean a content hash that redirects if it is deprecated?
- zcw100 4y agoAnd that's exactly what IPNS does. You can also use DNS with DNSLink.
- bawolff 4y agoIts what everyone does. The technique predates ipfs and friends by a long time.