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

RelayChainAccountId32Aliases #636

Open
xlc opened this issue Oct 24, 2021 · 3 comments · May be fixed by #651
Open

RelayChainAccountId32Aliases #636

xlc opened this issue Oct 24, 2021 · 3 comments · May be fixed by #651
Assignees

Comments

@xlc
Copy link
Member

xlc commented Oct 24, 2021

Add RelayChainAccountId32Aliases to xcm-support.

Similar to AccountId32Aliases from Polkadot, but also accept AccountId32 from relaychain.

Need to make sure not accepting AccountId32 from other parachains.

Need integration tests.

@zqhxuyuan
Copy link
Contributor

zqhxuyuan commented Nov 10, 2021

@zqhxuyuan
Copy link
Contributor

I've checked homa_lite config, and found type SovereignSubAccountLocation use create_x2_parachain_multilocation() which make form of (1, X1(AccountId)) , and it's like RelayChainAccountId32Aliases we add here to xcm-support. right? @xlc @syan095

@xlc
Copy link
Member Author

xlc commented Nov 11, 2021

RelayChainSovereignSubAccount represents a sub account of Karura sovereign account on relaychain. It is used to send KSM into this account to perform staking.

@zqhxuyuan zqhxuyuan linked a pull request Nov 15, 2021 that will close this issue
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 a pull request may close this issue.

2 participants