Use optimized map_to_curve_elligator2_curve448()
#1309
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.
This implements Elligator2 mapping according to RFC 9380 for Curve448 and Ed448.
The current Curve448 mapping was using either the unoptimized or an outdated version. For Ed448 we were currently using the isogeny mapping, which works correctly ofc. However, RFC 9380 specifically outlines an optimized mapping for Ed448 in combination of the Curve448 mapping. This avoids unnecessary inversions between mapping from Curve448 to Ed448.
While Curve448 will first be introduced in #1306, the Ed448 alligator mapping uses the Curve448 mapping.
I simply commented out
fn isoginy()
as it is now unused. However, it will be adapted in #1306 to facilitate Montgomery to Edwards conversions.