-
Notifications
You must be signed in to change notification settings - Fork 76
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
Plans to support bn254/bn128 #954
Comments
Hi there - can you describe the use-case you are looking to support with this signing curve? |
@non-fungible-nelson we (at EigenLabs/EigenLayer) use bn254 signatures types for aggregation purpose but was looking for something to support as remote signer. Operators running EigenDA use bn254 keys to attest the data and we use those signatures to aggregate and post onchain. |
Hi @non-fungible-nelson, I wanted to check in on this issue. It seems important for our ongoing work, and I'd love to get any updates. Thanks! |
@rohilsaraf97 we are working on a bn254 remote signer ourselves and just released an API spec - https://github.com/Layr-Labs/cerberus-api . Maybe this would be helpful to your project. we are gonna release the implementation soon which you can use. lmk if this helps |
Ah, this looks pretty recent! Thanks for this! I was working on making my own remote signer too, this makes my work easier. I'd love to contribute to your implementation! |
Will share once I open it ( likely coming week). Feel free to contribute! |
@rohilsaraf97 https://github.com/Layr-Labs/cerberus - very MVP implementation opened up. we will plan to add more features - feel free to suggest spec changes and features via discussions or issues :) and feel free to take them up once we are aligned |
Are there any plans to support bn254/bn128 curve https://hackmd.io/@jpw/bn254 ?
The text was updated successfully, but these errors were encountered: