Skip to content

Adds secp256k1_verify API #779

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

Merged
merged 103 commits into from
Feb 17, 2021
Merged

Adds secp256k1_verify API #779

merged 103 commits into from
Feb 17, 2021

Conversation

maurolacy
Copy link
Contributor

@maurolacy maurolacy commented Feb 9, 2021

Continuation / refactoring of #770.

Closes #780.

Creates a cosmwasm-crypto package, that can be imported from both, cosmwasm-std (for MockApi impls / tests) and cosmwasm-vm (for native impl of verification fns).

Uses platform-specific-dependencies to avoid importing / compiling cosmwasm-crypto for wasm32 targets.

Still requires:

  • Extended low level tests (wrong hash, wrong signature, wrong pubkey values / lengths).
  • Native imports tests.
  • API tests (basic).
  • Contract tests. Done in Crypto api contract #783.
  • Improved docs.

@maurolacy maurolacy force-pushed the crypto-api-package branch 2 times, most recently from 10cb8b1 to d50d2f4 Compare February 10, 2021 09:51
Copy link
Member

@webmaster128 webmaster128 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very good 🎉. Let's update this PR's title to make it specific to #780 and then merge.

@maurolacy maurolacy changed the title Crypto api package Adds secp256k1_verify API Feb 17, 2021
@webmaster128 webmaster128 added the automerge See mergify.io label Feb 17, 2021
@webmaster128 webmaster128 merged commit fda87cf into main Feb 17, 2021
@webmaster128 webmaster128 deleted the crypto-api-package branch February 17, 2021 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add secp256k1_verify API
2 participants