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

Move k256 backend into the crate #118

Merged
merged 9 commits into from Sep 19, 2022
Merged

Move k256 backend into the crate #118

merged 9 commits into from Sep 19, 2022

Conversation

LLFourn
Copy link
Owner

@LLFourn LLFourn commented Sep 14, 2022

The minimum change possible to remove the dependency. Still a lot of things to clean up.

  • Need to specify license of the backend code
  • Take some more recent changes from upstream
  • Delete unused feature flags.

@LLFourn LLFourn force-pushed the vendor-k256 branch 3 times, most recently from 26c172d to 0636536 Compare September 15, 2022 07:08
The minimum change possible to remove the dependency.
Still a lot of things to clean up.
purge all the old feature flags from the backend.
This was done by pasting the files over the original and looking at what
changed and then selectively adding those changes.
We're unable to fully update to it because it uses crypto-bigint to do
some scalar operations which we can't as a dependency.
This commit carefully incorporates the state of the upstream as much as possible.
It was extremely tedious work.
To avoid compiling two functions we do the same thing.
To make explaining licenses easier.
@LLFourn LLFourn merged commit 1f4dab2 into master Sep 19, 2022
@LLFourn LLFourn deleted the vendor-k256 branch September 19, 2022 07:34
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

Successfully merging this pull request may close these issues.

None yet

1 participant