3 ms·
Speed comparison from the BLAKE3 authors: https://github.com/BLAKE3-team/BLAKE3/ https://github.com/BLAKE3-team/BLAKE3/ I hadn't heard of BLAKE3 before (I thou
by lucb1e 7y ago
Speed comparison from the BLAKE3 authors: https://github.com/BLAKE3-team/BLAKE3/ https://github.com/BLAKE3-team/BLAKE3/
I hadn't heard of BLAKE3 before (I thought BLAKE2b was the latest and greatest), judging by commits from the repositories of that user it's about half a year old now.
Paper's abstract starts with:
> BLAKE3 [is] an evolution of the BLAKE2 cryptographic hash that is both faster and also more consistently fast across different platforms and input sizes. BLAKE3 supports an unbounded degree of parallelism, using a tree structure that scales up to any number of SIMD lanes and CPU cores. On Intel Cascade Lake-SP, peak single-threaded throughput is 4× that of BLAKE2b, 8× that of SHA-512, and 12× that of SHA-256, and it can scale further using multiple threads. BLAKE3 is also efficient on smaller architectures [like] 32-bit ARM1176
In the introduction, the reason for BLAKE3 is described:
> A drawback of BLAKE2 has been its large number of incompatible variants. The performance tradeoffs between different variants are subtle, and library support is uneven. BLAKE2b is the most widely supported, but it is not the fastest on most platforms. BLAKE2bp and BLAKE2sp are more than twice as fast on modern x86 processors, but they are sparsely supported and rarely adopted. BLAKE3 eliminates this drawback. It is a single algorithm with no variants
Paper: https://github.com/BLAKE3-team/BLAKE3-specs/ https://github.com/BLAKE3-team/BLAKE3-specs/ (By the way, the download doesn't work for me in the latest Firefox on Linux and GitHub's rendering is plain awful. Not sure if anyone else can reproduce that or if my Firefox is broken.)
- zahllos 7y agoThe reason you haven't heard of it before now is that it was released 2020-01-09, last Thursday at the time of writing, at Real World Crypto.
- lucb1e 7y agoThe only author of BLAKE3 that spoke there was JP (@veorq). The day matches but the title of his talk is "Too Much Crypto". Is that where it was announced? (Quick link to program: https://rwc.iacr.org/2020/program.html#day-2020-01-09 https://rwc.iacr.org/2020/program.html#day-2020-01-09)
- doomrobo 7y agoIt was announced in a lightning talk following that session
- lucb1e 7y agoThat doesn't sound very official. Most text in the paper seems to date from August, so it looks like this has been out for a while and was not only just announced, even if it was mentioned or officially "announced" (while being already released) in a surprise talk at that conference.
- baby 7y agoyup, Blake3 is 1-day old (released yesterday).
- oconnor663 7y agoJPA and I announced BLAKE3 at the RWC lightning talks, after JPA's Too Much Crypto talk, and we published all the repos and crates.io packages about 30 minutes prior to that. The commit history that you see in the repos was private until January 9.
- loeg 7y agoYou would be mistaken.
- mbar84 7y agoAn A4 booklet of the paper, if you're into printing out the interwebs: https://mbarkhau.keybase.pub/pdfs/blake3_a4_booklet.pdf?dl=1 https://mbarkhau.keybase.pub/pdfs/blake3_a4_booklet.pdf?dl=1