Use Extended/ExtensiblePoint
more appropriately
#1329
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently most mathematical operations on the twisted curve are implemented on
ExtensiblePoint
and take anExtendedPoint
as parameter. However, these operations often just convert to anExtendedPoint
internally (by multiplying T1 and T2).This PR moves operations to "where they belong" to make sure we don't unnecessarily call these conversions. This achieves removing 1 multiplication from Decaf point add/sub operations from previously 9 in total, so a ~10% performance improvement.
There are a couple of other operations that are affected negligibly: