-
Notifications
You must be signed in to change notification settings - Fork 26
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
Create a cache for BLS #453
Conversation
No dependency changes detected. Learn more about Socket for GitHub ↗︎ 👍 No dependency changes detected in pull request |
@matt-o-how I imagine the security warnings comes from just adding the |
a6c238b
to
6b58212
Compare
Pull Request Test Coverage Report for Build 9081446412Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
2c6a195
to
11c3527
Compare
this is a sensitive part of the consensus. we need really thorough tests and fuzzers. I think we should have some benchmarks as well |
update benchmark
…hia_rs into bls_cache_rebased
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you feel confident the unit tests cover all interesting cases?
A few cases are:
0% cache hit rate
100% cache hit rate
validating a signature of 0 messages and keys
validating a signature of 1 message and key
Can you think if any aspect that might benefit from fuzzing?
Creates a BLSCache struct and Py bindings for it.
Also adds a requirements.txt