Proof of concept #4
Merged
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
Co-authored-by: Navid TehraniFar <[email protected]>
Update standards, simplify COA bridging interface & intro project-specified URI view
Simplify proof of concept
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.
Closes: #1, #7
Description
This PR introduces the basis for future work, focussing on the Flow-native bridging use case as a proof of concept for moving assets between Flow & EVM environments. Metadata is not currently handled in the existing implementation, but could be added if deemed a blocker to merging into main.
As I understand it, the EVM environment is not yet build into the Cadence test framework so Cadence tests will follow. The framework for Solidity tests using foundry is included and additional test cases will follow this PR.
For contributor use:
masterbranchFiles changedin the Github PR explorer