Skip to content

Implement BLS12-381 point negation #1456

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

Merged
merged 10 commits into from
May 9, 2025

Conversation

jayz22
Copy link
Contributor

@jayz22 jayz22 commented Apr 3, 2025

What

Split out point negation part (0945897) from #1449, and address review comments on this part.

Why

Improves usability of the BLS12-381 features in a Groth16 verifier application (example contract)

  • Neg is an common operation, needed for using the proof parameter as pairing input, and is cheap and simple enough to be implemented as an sdk function.

Known limitations

[TODO or N/A]

@jayz22 jayz22 force-pushed the bls-point-negation branch from 7eb5bff to cfe74d4 Compare April 28, 2025 19:37
Copy link
Member

@leighmcculloch leighmcculloch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed the interface that developers will be exposed to and I think it looks good. I left just a couple minor comments for renaming functions to .to_ and implementing From instead of Into, and other traits to impl, and then one follow up issue for us to consider #1462.

@stellar/contract-committers Is someone from the core team able to review the internal BLS details?

@leighmcculloch leighmcculloch enabled auto-merge May 9, 2025 01:31
@leighmcculloch leighmcculloch added this pull request to the merge queue May 9, 2025
Merged via the queue into stellar:main with commit 13263e8 May 9, 2025
17 checks passed
@jayz22 jayz22 deleted the bls-point-negation branch May 9, 2025 03:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants