Reasons to Prefer Blake3 over Sha256

1. BLAKE3-specs

   1 8 179 0.0 HTML

   The BLAKE3 paper: specifications, analysis, and design rationale

   

   We go over some of our reasoning around that in section 7.5 of https://github.com/BLAKE3-team/BLAKE3-specs/blob/master/blak.... An early BLAKE3 prototype actually didn't include the chunk counter (https://github.com/oconnor663/bao/blob/master/docs/spec_0.9....), so I'm definitely sympathetic to the use cases that wish it wasn't there. However, after publication we found out that something like a chunk counter is necessary for the security of the Bao streaming verification tool: https://github.com/oconnor663/bao/issues/41. It could be that there's a design that's the best of both worlds, but I'm not sure.

2. Sevalla

   sevalla.com featured

   Deploy and host your apps and databases, now with $50 credit! Sevalla is the PaaS you have been looking for! Advanced deployment pipelines, usage-based pricing, preview apps, templates, human support by developers, and much more!

   

3. bao

   2 4 537 6.2 Rust

   an implementation of BLAKE3 verified streaming

   

   We go over some of our reasoning around that in section 7.5 of https://github.com/BLAKE3-team/BLAKE3-specs/blob/master/blak.... An early BLAKE3 prototype actually didn't include the chunk counter (https://github.com/oconnor663/bao/blob/master/docs/spec_0.9....), so I'm definitely sympathetic to the use cases that wish it wasn't there. However, after publication we found out that something like a chunk counter is necessary for the security of the Bao streaming verification tool: https://github.com/oconnor663/bao/issues/41. It could be that there's a design that's the best of both worlds, but I'm not sure.

4. BLAKE3

   3 37 5,760 8.7 Assembly

   the official Rust and C implementations of the BLAKE3 cryptographic hash function

   

   > might be easier with a public domain license instead of the current ones

   There reference implementation is public domain (CC0) or at your choice Apache 2.0

   https://github.com/BLAKE3-team/BLAKE3/blob/master/LICENSE

5. multihash

   4 10 926 5.0 Shell

   Self describing hashes - for future proofing

   

   Since you seem to have done a fair bit of research in this area, do you have any opinions or thoughts about the Multihash format?

   https://multiformats.io/multihash/

   It fills in some of the blanks in your "prefixing the hash with the value of the enum for the hash" step.

6. go-benchmarks

   5 1 10 1.9 Go

   Comprehensive and reproducible benchmarks for Go developers and architects. (by skerkour)

   

   At the end of the day, what matters really for most people is

   1) Certifications (FIPS...)

   2) Speed.

   SHA-256 is fast enough for maybe 99,9% of use cases as you will saturate your I/O way before SHA-256 becomes your bottleneck[0][1]. Also, from my experience with the different available implementations, SHA-256 is up to 1.8 times faster than Blake3 on arm64.

   [0] https://github.com/skerkour/go-benchmarks/blob/main/results/...

   [1] https://kerkour.com/fast-hashing-algorithms

7. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

Suggest a related project