Re:Multihash – self-describing hashes
by _prometheus on Sunday February 26, 2017 @05:11PM
(#13740290)
Truncations happen in many sizes. The combinations here are not helpful: N functions * M commonly chosen sizes. Simple assumptions: 20 functions * 10 sizes = 200 codes. already not good.
You can print a human-readable version of multihash as:
sha2-256-20B-<hex>
Using the same values of the table. But again, it is preferable that it travels in-band with the values, as otherwise it will likely get chopped up and placed into out of band context.
You don't have to support hashing with all hash functions. In theory you could accept just few (and thus have their implementations) and error out in case of one that is not supported comes through.
What are the benefits of using Multihash?