Zooko🛡️
Zooko🛡️
@zooko.bsky.social
You gotta not let go but you also gotta not hang on too tight. Hold it just right as she goes.
On http://bench.cr.yp.to/results-hash.html#aarch64-pi4b, BLAKE3 is one of the most efficient secure hash functions, but in reality BLAKE3 is much *more* efficient than shown there, because it uses ARM NEON (which is not shown in that benchmark) and because of the new BLAKE3 v1.4.1 speedups.
July 7, 2023 at 12:55 AM
BLAKE3 is now *even* faster on (some) ARM machines: https://github.com/BLAKE3-team/BLAKE3/releases/tag/1.4.1
July 6, 2023 at 10:08 PM
@elonmusk I demand the return of the Fail Whale!
July 1, 2023 at 9:04 PM
New OpenZFS release candidate just dropped with BLAKE3 as a checksum.

https://phoronix.com/news/OpenZFS-2.2-rc1

This is another example of software engineers upgrading from weak/insecure algorithms to BLAKE3 (which is secure) due to BLAKE3's performance.

⤵️
July 1, 2023 at 9:00 PM
Hey im back cuz twitter is ratelimiting me and i wanna tell everyone how awesome BLAKE3 is
July 1, 2023 at 8:56 PM
Thanks, tqbf. I'm guessing you missed the second half because of this UI on this app, where the second half of the thread is hidden behind an innocuous "Continue thread…":

/cc @pfrazee.com
May 27, 2023 at 12:29 AM
May 7, 2023 at 7:23 PM
Mashing reload on http://bench.cr.yp.to/web-impl/amd64-beelink-crypto_hash.html to see when the new hash function benchmarks are going to drop.

(Jack @oconnor663.bsky.social O'Connor has submitted a patch for a problem in the bench.cr.yp.to benchmarks of BLAKE3.)
May 7, 2023 at 5:51 PM
May 6, 2023 at 2:11 AM
Sorry deep links to specific posts on my blog are broken, but if you search long and hard you might be able to find this post: https://tahoe-lafs.org/~warner/blog.html#%5B%5Bcan%20we%20build%20a%20crypto%20system%20to%20last%20for%20a%20hundred%20years%3F%5D%5D
May 5, 2023 at 7:37 PM
May 5, 2023 at 2:17 AM
May 5, 2023 at 12:27 AM
May 2, 2023 at 1:02 AM
According to http://bench.cr.yp.to/web-impl/amd64-icelake2-crypto_hash.html the SSE impl of BLAKE3 should be only about 25% slower than the AVX512 impl on IceLake. So something really doesn't add up.
May 2, 2023 at 12:50 AM
Hmmm… am i reading this paper right? This seems to say that the SSE impl of BLAKE3 on IceLake took 57 cpb on 64 b, but the AVX512 impl of BLAKE3 on IceLake on http://bench.cr.yp.to/results-hash.html#amd64-icelake2 took <3 cpb on 64 b.
May 2, 2023 at 12:46 AM
You can see SHA3 in this graph. In the future there will probably be modest improvements in SHA3 performance, due to SHA3 circuits in chips, but there will probably be bigger improvements in BLAKE3 performance, due to parallelization: https://bsky.app/profile/zooko.bsky.social/post/3jum3aczmtg2m
May 2, 2023 at 12:33 AM
Contrast with the legacy web site, where when i post two links the first one disappears and will probably be overlooked by 99% of readers: https://twitter.com/zooko/status/1652869524344164353
May 1, 2023 at 3:48 AM
BLAKE3 is *much* more efficient (in time and energy) than SHA256, like 14 *times* as efficient in typical use cases on typical platforms.
April 30, 2023 at 4:33 PM
BLAKE (the original) was very well-studied during the SHA3 competition. In NIST's final report on the SHA3 process, they stated that the depth of scientific analysis applied to BLAKE exceeded even that applied to Keccak (the final SHA3 winner)
April 30, 2023 at 4:31 PM