Skip to content

recommend BLAKE3 instead of BLAKE2 #703

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zookoatshieldedlabs
Copy link

Reasons:

  • BLAKE3 has been out for 5 years now.
  • No further cryptanalytic results have come out indicating that it might not be secure (nor for BLAKE2, nor BLAKE, nor ChaCha20, nor Salsa20).
  • BLAKE3 has a major, qualitative efficiency improvement, which is the Merkle Tree structure, allowing (but not requiring) any amount of parallelism.
  • BLAKE3 is already extensively adopted in many different projects in many different industries/areas/niches.
  • BLAKE3 is currently being more actively maintained, as in patches are being accepted by the chief maintainer, Jack "@oconnor663" O'Connor. https://github.com/BLAKE3-team/BLAKE3/commits/master/

P.S. Hi, Tony! :-)

Reasons:
 * BLAKE3 has been out for 5 years now.
 * No further cryptanalytic results have come out indicating that it might not be secure (nor for BLAKE2, nor BLAKE, nor ChaCha20, nor Salsa20).
 * BLAKE3 has a major, qualitative efficiency improvement, which is the Merkle Tree structure, allowing (but not requiring) any amount of parallelism.
 * BLAKE3 is already extensively adopted in many different projects in many different industries/areas/niches.
 * BLAKE3 is currently being more actively maintained, as in patches are being accepted by the chief maintainer, Jack "@oconnor663" O'Connor. https://github.com/BLAKE3-team/BLAKE3/commits/master/

P.S. Hi, Tony! :-)
@zookoatshieldedlabs
Copy link
Author

P.S. You might be interested to know that I found this repo from https://github.com/0xPolygonHermez/zisk-patch-hashes

@tarcieri
Copy link
Member

tarcieri commented Jul 6, 2025

I'm fine with this, although it should probably link to the BLAKE3 repository since it's not in-tree.

Curious what @newpavlov thinks.

@newpavlov
Copy link
Member

I agree that we should link the BLAKE3 repo. I am fine with recommending BLAKE3 instead of BLAKE2, especially considering that our current implementation is not great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants