migrate field from in-house goldilocks to plonky3 #805
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hero78119
force-pushed
the
feat/plonky3_field
branch
from
6bd1ed7 to
1c3a5b6
Compare
matthiasgoergens
changed the title
|
How close is this to passing our CI? |
This PR only migrate |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to #806
Changes highlights
mpcs,poseidon. We will remove crateposeidonin the future, as right now onlympcsdepends on it.transcriptstop3::poseidon. We can upgrade toposeidon2later.p3::Fieldinstead offf:Field, and adjust respective api:E::from->from_canonical_u64.E::from -> from_basesumcheck/mle both all unittest passed.