Skip to content
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

Potential optimization for the torsion check #651

Open
randombit opened this issue Apr 30, 2024 · 1 comment
Open

Potential optimization for the torsion check #651

randombit opened this issue Apr 30, 2024 · 1 comment

Comments

@randombit
Copy link
Contributor

Currently the torsion check (is_torsion_free) is implemented using a variable base constant time multiplication. However the group order is public so there is no need for side channel countermeasures regarding the scalar. This would save the overhead from LookupTable::select, both the constant time lookup as well as the cost of doing the point negation in the case it's not needed. You could also precompute the NAF encoding of the group order, though I'm not sure if that's worthwhile.

@randombit
Copy link
Contributor Author

#657

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

No branches or pull requests

1 participant