-
Notifications
You must be signed in to change notification settings - Fork 23
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
[Release needed] BLS tests: fast_aggregate_verify inconsistent format v1.0.0-rc0 #22
Comments
Fixed by ethereum/consensus-specs#2099 but I guess we need a new release for those who uses the tarballs directly. For now I'll edit manually in my downloaded files |
mratsim
added a commit
to status-im/nim-blscurve
that referenced
this issue
Oct 26, 2020
mratsim
added a commit
to status-im/nim-blscurve
that referenced
this issue
Oct 26, 2020
* Update vectors to BLSv4 v1.0.0-rc0 [skip ci] * Workaround ethereum/consensus-spec-tests#22, ethereum/consensus-specs#2099 * Rework BLSv4 API ethereum/consensus-specs#2080 and address #76 #77 * Upgade Milagro vectors * Upgrade BLST backend with new API * BLST forgot to return true for publicFromSecret
3 tasks
fixed in v1.0.0 tests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is one test in fast_aggregate_verify that has an inconsistent format with the rest (fast_aggregate_verify_infinity_pubkey)
It uses
messages
(plural) instead ofmessage
The text was updated successfully, but these errors were encountered: