just more complexity for no reason
the amount of times hash functions are called in these things is far less than requires serious optimization
just stick to one hash
and just stick to one network transport and encoding for as long as possible, and let someone else manage that shit
igaf about blake3 it's not that much better and not better in the regular implementation than sha256 in the SIMD implementation
blake3's main selling point is performance, its collision resistance and preimage resistance are considered to be about equal
when your codebase is already using SHA256 every further hash you want to add is interface complexity and execution complexity
without a compelling reason to do it, better to upgrade to SIMD than ADD blake3
pear uses their own merkle hash using blake 2b because it is faster than blake3 https://github.com/holepunchto/hypercore/blob/main/lib/merkle-tree.js
https://github.com/holepunchto/hypercore-crypto/blob/main/index.js
blake2b as crypto_generichash from libsodium https://libsodium.gitbook.io/doc/hashing/generic_hashing
