-
Notifications
You must be signed in to change notification settings - Fork 2
feat: bls12_381 that support zkvm-pico #4
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
feat: bls12_381 that support zkvm-pico #4
Conversation
|
@ArtiomTr this PR is good to review. |
.editorconfig
Outdated
| @@ -0,0 +1,24 @@ | |||
| root = true | |||
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.
I think this is not really necessary, it is better to keep changes as small as possible, as it is just patch for original dependency, not a fork of it
benches/hash_to_curve.rs
Outdated
| #[cfg(not(feature = "zkvm-pico"))] | ||
| <G1Projective as HashToCurve<ExpandMsgXmd<sha2::Sha256>>>::encode_to_curve( | ||
| [black_box(message)], | ||
| black_box(dst), | ||
| ) | ||
| ); | ||
| #[cfg(feature = "zkvm-pico")] | ||
| <G1Projective as HashToCurve<ExpandMsgXmd<sha2::Sha256>>>::encode_to_curve( | ||
| black_box(message), | ||
| black_box(dst), | ||
| ); |
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.
So this needs to be unified - single HashToCurve api, not two different versions for different backends
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.
unified now.
…vm-pico features.
… into zkcrypto/bls12_381
This PR is built on top of PR #2 by @Dyslex7c
Check the latest CI test and lint here:
https://github.com/jimmychu0807/grandine-universal-precompiles/actions