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

Add default implementations for secp256r1_verify/secp256r1_recover_pubkey #2058

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

webmaster128
Copy link
Member

Part of #2001

@webmaster128 webmaster128 requested a review from aumetra March 17, 2024 23:43
@webmaster128 webmaster128 mentioned this pull request Mar 17, 2024
13 tasks
Copy link
Member

@aumetra aumetra left a comment

Choose a reason for hiding this comment

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

Looks fine and also makes sense to not break downstream impls. But on that subject, is it even expected that people implement these traits themselves?

If not, then we should probably seal these traits next breaking release. That way we can do anything we want with these traits.

@webmaster128
Copy link
Member Author

Contract developers don't implement then usually. However, if you build a testing framework and have your own version of MockApi with custom behaviour you need to implement it on the caller side. I don't know if those cases actually exist yet but we should support it.

@webmaster128 webmaster128 merged commit 4060b2c into main Mar 18, 2024
28 of 29 checks passed
@webmaster128 webmaster128 deleted the unimplemented-api branch March 18, 2024 09:25
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.

2 participants