Move multi_miller_loop
and final_exponentiation
into BW6Config
#542
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.
Description
This PR implements the steps analagous to the PR #534 for the BW6 model. The motivation os further outlined in issue #537 :
This PR moves the implementation of the functions
multi_miller_loop
andfinal_exponentiation
in theBW6
model from thePairing
trait into theBW6Parameters
trait. Here they serve as default implementations, which are then referenced in the Pairing implementation forBW6
.This way we can overwrite the default implementations for both functions when we define model curves for the BW6 model. The motivation for this is like the one in #528 : we can provide our own implementations on platforms on which elliptic curve arithmetic is slow or for the case os specialized hardware.
closes: #XXXX
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
- [ ] Wrote unit testsPending
section inCHANGELOG.md
Files changed
in the GitHub PR explorer