Use AccountId20 type#20
Closed
JoshOrndorff wants to merge 19 commits into
Closed
Conversation
This was referenced Jun 24, 2023
Closed
* add some known prefilled account to dev node * fix Lookup and Address
Collaborator
Author
|
Closing this in favor of #26 . if / when unified accounts go in, it should be with frontier of course. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR switches the chain's native account id type to be
AccountId20which is the same one Moonbeam uses.This is in preparation for evm support in #9. The evm requires eth-style account ids, and if we can use the same ones in the runtime, then we don't have the make users map them together and handle the corresponding edge cases.