Benjamin Goering

@kritzcreek would you ever consider changing the motoko-base release process to publish git tags that follow semver syntax? https://semver.org/ From github.com [docs](https://docs.github.com/en/github/administering-a-repository/managing-releases-in-a-repository). > Type a version number for your release....

What do you think about including example usage of these or, better, a test? (I don't know if it's even possible to add a test in motoko)

Regardless of what to hyperlink to, does the reference generally refer to the same thing as what [other DIF repos](https://github.com/search?q=org%3Adecentralized-identity%20multihash&type=code) name 'multihash'? i.e. https://multiformats.io/multihash/ - if so, you may want...

A good link may be https://www.ietf.org/archive/id/draft-multiformats-multihash-07.html See also this fledgling ietf wg https://datatracker.ietf.org/wg/multi/about/

> Minimally we should allow for the defaults currently generated by ipfs add --cid-version 1, which is base32 sha2-256 dag-pb for chunked files > 256*1024 bytes, and base32 sha2-256 raw...

> Do you know of any other projects with similar requirements moving this direction? Here are some projects using exclusively blake3 for hashing * https://www.iroh.computer/design/content-addressing/ * https://docs.sfive.net/concepts/content-addressed-data.html * https://github.com/firedancer-io/specs/blob/ripatel/stl-draft/p2p/STLv1_0.md#34-handshake-protocol Here...

Personally I don’t know of a strong reason to support BLAKE-2b in addition to BLAKE3 + SHA

> However, to do so, we should consider naming the address field within the Avro object more generically, and specify the format alongside the resource type enum so that consuming...

This has been rolled over from each milestone for several months . Is it really ongoing or is it blocked somehow? Will I be able to use a feature like...

I'm interested in scouting this out but not till landing https://github.com/web3-storage/migrate-to-w3up/pull/3