-
Notifications
You must be signed in to change notification settings - Fork 25
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
Road to 1.0? #28
Comments
Remarkable timing: There's going to be an announcement about this next week. The output will definitely change at that point, but after that I expect it to be stable. |
That's awesome to hear! I'l be looking forward to it. |
We announced the BLAKE3 hash function on January 9, and I released Bao 0.10.0 at the same time. Bao is now based on BLAKE3, and (barring the embarrassing discovery of a vulnerability in BLAKE3) the output is stable. Using Bao in production today would be a tad aggressive, since there are no existing production users, and the code hasn't been audited by anyone. (Being an open source project, I also don't have anything resembling a budget to pay for an audit.) But I think now would be a fine time to start prototyping :) |
I'm eager to use Bao in a project, so I'm curious about its current state, and when it might be ready for use. I read through the spec, and it seems pretty solid. Are there unresolved questions about the design, or is it mostly a question of getting more review at this point?
I'd be using it in a context where the quality of the implementation is less important than the stability of the output. I.e. it would be fine if the implementation isn't optimal, as long as the output of the hash function doesn't change.
The text was updated successfully, but these errors were encountered: