updates crypto libs to the next version #17
Merged
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.
closes #15
Description
The docknetwork crypto libraries have moved ahead, and with 3 new minor versions. This PR updates those libraries only by one version, and two more PRs are coming to update these libraries to the latest versions.
In multiple cases, we've noticed that the API of the dock crypto crates have changed a bit, (mostly typing except in one case). We've updated those types, and added the missing methods, to make sure all tests pass as before. Please review these changes carefully, as I could delve deeper into how why work to make the best judgment.
PR checklist
yarn install; yarn build; yarn test
to make sure everything runs as before.Does this PR introduce a breaking change?
I had to let go of the legacy proof system as it used an out-of-date wasmer version that is incompatible with the new versions of the libraries
Which merge strategy will you use?