multihash support in swarm about swarm HOT 9 CLOSED

I'll start:

Pros: allows multi-hashes to be stored in ENS making it easy to use ENS with swarm and ipfs and other p2p storage solutions.

Cons: Makes ENS registration a little more expensive (store two words instead of one because multihash is longer than a swarm hash)

from swarm.

I'd like to see Swarm move to Multihash for ENS, at least, because it would allow us to have a single resolver profile for all content-addressed networks, and because it provides an upgrade path for changes in hash function.

from swarm.

Is the proposal only for root hashes or also for intermediate chunk hashes in low-level Merkle trees?

from swarm.

I must admit that I'm not entirely sure how multihashes look. I understand that it is a hash with metadata about what type of hash it is.
Thus I thought we could keep the internal structure of swarm intact and just use the longer multihashes (swarm hash + extra data?) as roothashes stored on ENS.

from swarm.

the metadata bytes should be a separate data field from the hash value itself

storing metadata should be optional, meaning I should be able to only pay for / use 32 bytes if I want to.

As long as we open this discussion, another question that follows is should ENS allow for even longer data values than this? In fact, should it allow for arbitrary values? Let's say someone comes along who wants to use ENS with some scheme that uses 512 bit or 1024 bit hashes? The latter would thus require 5 data fields.

Yes, internally in swarm we should definitely keep the hash as-is.

from swarm.

should ENS allow for even longer data values

That's a question about the resolver contracts. As such it is possible to write a resolver that stores any data.
The current discussion pertains to the content() field of the default resolver contract. How can we use it to store hash such that we can easily use Swarm and IPFS and other hash-based storage networks?

from swarm.

ok I dont see a problem with using multihash in ENS.
As long as intermediate hashes of the swarm hash as well as hashes in manifest entries remain 32 byte long

from swarm.

but doesn't the ens entry have to be a swarm root hash?

from swarm.

@zelig
as we discussed at the cafe today: let' s do it:
#186

from swarm.