Skip to content

crypto: call batchVerificationImpl from OneTimeSignatureVerifier.Verify #3759

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 1 commit into from
Mar 12, 2022

Conversation

cce
Copy link
Contributor

@cce cce commented Mar 11, 2022

Summary

The ed25519 batch verification implementation in #3031 provides a performance improvement for validating multiple signatures (such as multiple transaction signatures). Since each OneTimeSignature (used by agreement votes) is actually 3 ed25519 signatures, this hooks up its verifier to the batch verification implementation, yielding a ~12% performance improvement in the included benchmark on my computer.

Test Plan

Added benchmark, existing tests should pass.

@cce cce requested a review from id-ms March 11, 2022 21:11
@cce cce self-assigned this Mar 11, 2022
@tsachiherman tsachiherman merged commit 88e8b96 into algorand:master Mar 12, 2022
@cce cce deleted the batch-verify-onetimesig branch March 12, 2022 16:40
jannotti pushed a commit to jannotti/go-algorand that referenced this pull request Mar 13, 2022
…rand#3759)

Summary
The ed25519 batch verification implementation in algorand#3031 provides a performance improvement for validating multiple signatures (such as multiple transaction signatures). Since each OneTimeSignature used by agreement votes is actually 3 ed25519 signatures, this hooks up the verifier to the batch verification implementation, yielding a ~12% performance improvement in the included benchmark on my computer.

Test Plan
Added benchmark, existing tests should pass.
@algojack algojack mentioned this pull request Mar 15, 2022
tmc pushed a commit to tmc/go-algorand that referenced this pull request Mar 7, 2025
…rand#3759)

Summary
The ed25519 batch verification implementation in algorand#3031 provides a performance improvement for validating multiple signatures (such as multiple transaction signatures). Since each OneTimeSignature used by agreement votes is actually 3 ed25519 signatures, this hooks up the verifier to the batch verification implementation, yielding a ~12% performance improvement in the included benchmark on my computer.

Test Plan
Added benchmark, existing tests should pass.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants