Add Crypto contract #456
Merged
Add Crypto contract #456
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
This was referenced Oct 17, 2024
joshuahannan
approved these changes
Oct 18, 2024
|
@joshuahannan Yes, it would be great to improve the contracts. Once we have put it on chain it should be much easier |
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.
Work towards onflow/cadence#3135
Test case is adapted from https://github.com/onflow/flow-go-sdk/blob/7eb6328b774496418310a8487a893c070c9e5367/examples/verify_signature/user_signature/main.go.
The
Cryptocontract code and the Cadence-based tests were originally located in the Cadence codebase, and are going to be removed from there in onflow/cadence#3619. The contract code and test code was moved as-is.