Solidity encoding for XCM types in precompiles utils #1246
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
librelois
approved these changes
Nov 10, 2023
|
@sorpaas can you give a review to this please? |
|
@sorpaas can you review this PR? Or ping someone else that can do it? |
sorpaas
approved these changes
Jan 4, 2024
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.
Port Moonbeam's precompile utils encoding for XCM types to Frontier.
This was previously avoided in #1150 as it depends on
staging-xcm, which was previously on thepolkadotrepository and would have added an new dependency to Frontier. But now that the repos have been merged it no longer carries that weight.