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

Maintain transfer channel before/after sovereign -> consumer changeover #782

Closed
Tracked by #756
shaspitz opened this issue Mar 15, 2023 · 0 comments · Fixed by #832
Closed
Tracked by #756

Maintain transfer channel before/after sovereign -> consumer changeover #782

shaspitz opened this issue Mar 15, 2023 · 0 comments · Fixed by #832
Assignees

Comments

@shaspitz
Copy link
Contributor

shaspitz commented Mar 15, 2023

Transfer channel needs to be maintained through the migration. New transfer channel would result in undesirable legacy denoms

@shaspitz shaspitz changed the title Transfer channel is maintained through the migration. New transfer channel would result in undesirable legacy denoms (first iteration: no provider changes. Do this in separate PR to main) Maintain transfer channel before/after sovereign -> consumer migration Mar 15, 2023
@shaspitz shaspitz changed the title Maintain transfer channel before/after sovereign -> consumer migration Maintain transfer channel before/after sovereign -> consumer changeover Mar 15, 2023
@shaspitz shaspitz self-assigned this Apr 4, 2023
@shaspitz shaspitz linked a pull request Apr 12, 2023 that will close this issue
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant