{"slug": "blake3", "name": "BLAKE3", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 4, "commenters": 7, "warners": 0, "score": 4.02, "rising": 0.02, "first": "2025-11-07", "latest": "2026-08-31", "why": "Thanks for making BLAKE3! I use it in several pieces of software.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 1, "compare": 2, "warn": 0}, "spark": [2, 0, 1, 0, 0, 0, 0, 0, 0, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "Thanks for making BLAKE3! I use it in several pieces of software.", "kind": "", "icon": true, "domain": null, "github_repo": "github.com/blake3-team/blake3", "official_url": "https://github.com/BLAKE3-team/BLAKE3", "pricing": "", "aliases": ["BLAKE3", "blake3"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 792129552, "item_id": 49508097, "url": "https://news.ycombinator.com/item?id=49508097", "by": "TacticalCoder", "date": "2026-08-31", "stance": "recommend", "quote": "Blake3 is really a wonderfully fast cryptographic hash.", "excerpt": "> deduplication at the file level: every file is now stored under its BLAKE3 hash Blake3 is really a wonderfully fast cryptographic hash. I use it for my own \"deduplication / integrity / berzerker\" utility (which I made before LLMs were a thing). If I've got a file named: DSC98731-b3-7b39197a22.JPG then: - if that file doesn't checksum back to 7b39197a22 there's a file integrity problem (amazing and it already helped", "context": "built own dedup utility", "use_case": "file deduplication and integrity", "switched_from": "", "story": "uv: Deduplicate all files in the wheel cache"}, {"id": 748480912, "item_id": 46780057, "url": "https://news.ycombinator.com/item?id=46780057", "by": "jrockway", "date": "2026-01-27", "stance": "recommend", "quote": "BLAKE3 would probably make a noticeable performance difference.", "excerpt": "sha256 is a very slow algorithm, even with hardware acceleration. BLAKE3 would probably make a noticeable performance difference. Some reading from 2021: https://jolynch.github.io/posts/use_fast_data_algorithms/ It is really hard to describe how slow sha256 is. Go sha256 some big files. Do you think it's disk IO that's making it take so long? It's not, you have a super fast SSD. It's sha256 that's slow.", "context": "", "use_case": "", "switched_from": "", "story": "I made my own Git"}, {"id": 736860864, "item_id": 46053804, "url": "https://news.ycombinator.com/item?id=46053804", "by": "EnPissant", "date": "2025-11-25", "stance": "recommend", "quote": "Thanks for making BLAKE3! I use it in several pieces of software.", "excerpt": "Yeah, I was objecting to this part: > If you have a file and the BLAKE3 hash of that file To me that means the final hash. If you have the full tree of hashes that is a different story! PS. Thanks for making BLAKE3! I use it in several pieces of software.", "context": "", "use_case": "hash function in software", "switched_from": "", "story": "Choosing a hash function for 2030 and beyond: SHA-2 vs. SHA-3 vs. BLAKE3"}, {"id": 733515680, "item_id": 45844730, "url": "https://news.ycombinator.com/item?id=45844730", "by": "zazaulola", "date": "2025-11-07", "stance": "recommend", "quote": "Try Blake3 instead SHA-1", "excerpt": "Try Blake3 instead SHA-1 https://github.com/BLAKE3-team/BLAKE3", "context": "", "use_case": "Hashing, replacing SHA-1", "switched_from": "", "story": "Two billion email addresses were exposed"}]}], "caveats": [], "who": [{"by": "TacticalCoder", "context": "built own dedup utility", "url": "https://news.ycombinator.com/item?id=49508097", "date": "2026-08-31"}], "tags": [], "use_cases": ["file deduplication and integrity", "hash function in software", "hashing, replacing sha-1"], "compared": [], "makers": [{"id": 736830128, "item_id": 46051883, "url": "https://news.ycombinator.com/item?id=46051883", "by": "oconnor663", "date": "2025-11-25", "stance": "recommend", "quote": "BLAKE3 does reduce the round count relative to BLAKE2", "excerpt": "BLAKE3 does reduce the round count relative to BLAKE2, and the underlying compression functions are similar enough that it is an apples-to-apples comparison. Our rationale for doing that was described in https://eprint.iacr.org/2019/1492.pdf, which also argued that Keccak could reduce their round count even farther than they did.", "context": "", "use_case": "", "switched_from": "", "story": "Choosing a hash function for 2030 and beyond: SHA-2 vs. SHA-3 vs. BLAKE3"}, {"id": 736829568, "item_id": 46051848, "url": "https://news.ycombinator.com/item?id=46051848", "by": "oconnor663", "date": "2025-11-25", "stance": "recommend", "quote": "This is a difference between BLAKE3 and most other hash functions.", "excerpt": "This is a difference between BLAKE3 and most other hash functions. In the usual arrangement (\"Merkle\u2013Damg\u00e5rd\"), each block depends on the previous one, so the only way to verify some \"slice\" of the input is to re-hash the whole thing. But when you arrange the input into a tree shape (a \"Merkle tree\") instead, suddenly the right half of the tree does not depend on the left half until the very last step at the very top", "context": "", "use_case": "Verifiable file hashing", "switched_from": "", "story": "Choosing a hash function for 2030 and beyond: SHA-2 vs. SHA-3 vs. BLAKE3"}], "threads": [{"url": "https://news.ycombinator.com/item?id=46047409", "title": "Choosing a hash function for 2030 and beyond: SHA-2 vs. SHA-3 vs. BLAKE3", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=49506142", "title": "uv: Deduplicate all files in the wheel cache", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48386343", "title": "Show HN: Rscrypto, pure-Rust crypto with industry leading public benches", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47521832", "title": "item 47521832", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47286408", "title": "Filesystems Are Having a Moment", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46778341", "title": "I made my own Git", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 2}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {}, "2026-03": {"compare": 1, "neutral": 1}, "2026-04": {}, "2026-05": {}, "2026-06": {"compare": 1}, "2026-07": {}, "2026-08": {"recommend": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 792129552, "item_id": 49508097, "url": "https://news.ycombinator.com/item?id=49508097", "by": "TacticalCoder", "date": "2026-08-31", "stance": "recommend", "quote": "Blake3 is really a wonderfully fast cryptographic hash.", "excerpt": "> deduplication at the file level: every file is now stored under its BLAKE3 hash Blake3 is really a wonderfully fast cryptographic hash. I use it for my own \"deduplication / integrity / berzerker\" utility (which I made before LLMs were a thing). If I've got a file named: DSC98731-b3-7b39197a22.JPG then: - if that file doesn't checksum back to 7b39197a22 there's a file integrity problem (amazing and it already helped", "context": "built own dedup utility", "use_case": "file deduplication and integrity", "switched_from": "", "story": "uv: Deduplicate all files in the wheel cache"}, {"id": 774183970, "item_id": 48386498, "url": "https://news.ycombinator.com/item?id=48386498", "by": "LoadingALIAS", "date": "2026-06-03", "stance": "compare", "quote": "the official `blake3` crate", "excerpt": "I've built rscrypto because crypto kept being where my Rust database stopped being portable: different stack on the server, different target story on WASM, different answer on RISC-V/POWER/IBM Z, and a different audit surface every time I added a primitive. The supply chain risk, given the landscape we're in today, was too high. v0.3.1 is one feature-selected crate. Leaf features when you need one primitive (`sha2`, ", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: Rscrypto, pure-Rust crypto with industry leading public benches"}, {"id": 760349328, "item_id": 47521833, "url": "https://news.ycombinator.com/item?id=47521833", "by": "1trillionbrckts", "date": "2026-03-25", "stance": "neutral", "quote": "hashed the entire 8-terabyte dataset using BLAKE3", "excerpt": "Before this year's NCAA tournament tipped off, I generated one trillion brackets using weighted probabilities derived from sportsbooks and KenPom. I then hashed the entire 8-terabyte dataset using BLAKE3 into a Merkle root and posted it to the Ethereum blockchain on March 17, creating an immutable timestamp proving the data existed before any games were played. Even though only 48 games have been played, and the reco", "context": "", "use_case": "", "switched_from": "", "story": null}, {"id": 756634064, "item_id": 47289629, "url": "https://news.ycombinator.com/item?id=47289629", "by": "ciupicri", "date": "2026-03-07", "stance": "compare", "quote": "Why Blake3 and not say XXH3 64/128 bits", "excerpt": "Why Blake3 and not say XXH3 64/128 bits (https://xxhash.com/)?", "context": "", "use_case": "", "switched_from": "", "story": "Filesystems Are Having a Moment"}, {"id": 748480912, "item_id": 46780057, "url": "https://news.ycombinator.com/item?id=46780057", "by": "jrockway", "date": "2026-01-27", "stance": "recommend", "quote": "BLAKE3 would probably make a noticeable performance difference.", "excerpt": "sha256 is a very slow algorithm, even with hardware acceleration. BLAKE3 would probably make a noticeable performance difference. Some reading from 2021: https://jolynch.github.io/posts/use_fast_data_algorithms/ It is really hard to describe how slow sha256 is. Go sha256 some big files. Do you think it's disk IO that's making it take so long? It's not, you have a super fast SSD. It's sha256 that's slow.", "context": "", "use_case": "", "switched_from": "", "story": "I made my own Git"}, {"id": 736860864, "item_id": 46053804, "url": "https://news.ycombinator.com/item?id=46053804", "by": "EnPissant", "date": "2025-11-25", "stance": "recommend", "quote": "Thanks for making BLAKE3! I use it in several pieces of software.", "excerpt": "Yeah, I was objecting to this part: > If you have a file and the BLAKE3 hash of that file To me that means the final hash. If you have the full tree of hashes that is a different story! PS. Thanks for making BLAKE3! I use it in several pieces of software.", "context": "", "use_case": "hash function in software", "switched_from": "", "story": "Choosing a hash function for 2030 and beyond: SHA-2 vs. SHA-3 vs. BLAKE3"}, {"id": 733515680, "item_id": 45844730, "url": "https://news.ycombinator.com/item?id=45844730", "by": "zazaulola", "date": "2025-11-07", "stance": "recommend", "quote": "Try Blake3 instead SHA-1", "excerpt": "Try Blake3 instead SHA-1 https://github.com/BLAKE3-team/BLAKE3", "context": "", "use_case": "Hashing, replacing SHA-1", "switched_from": "", "story": "Two billion email addresses were exposed"}]}