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.

Sign up for GitHub

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

Jump to bottom

Support IBC in Governance #3359

Closed
2 of 5 tasks
Tracked by #3358
aubrika opened this issue Nov 15, 2023 · 1 comment
Closed
2 of 5 tasks
Tracked by #3358

Support IBC in Governance #3359

aubrika opened this issue Nov 15, 2023 · 1 comment
Labels
_P-V1 Priority: slated for V1 release

Comments

@aubrika
Copy link
Contributor

aubrika commented Nov 15, 2023 •
edited
Loading

Why this feature is required pre-mainnet

Governance must be able to manage IBC configurations in the case of unplanned counterparty upgrades (or counterparty exploit and/or hardfork). Having full support for governance of IBC is necessary at mainnet otherwise users of the network may encounter undesirable behavior such as being unable to transfer funds via IBC to certain counterparties.

What we need to implement
@aubrika aubrika mentioned this issue Nov 15, 2023
Closed
2 tasks
@aubrika aubrika added the _P-V1 Priority: slated for V1 release label Nov 15, 2023
@erwanor
Copy link
Member

erwanor commented Jan 4, 2024

Closing in favor of #2173

@erwanor erwanor closed this as completed Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
_P-V1 Priority: slated for V1 release
Projects
No open projects
Testnets
Status: Testnet 63: Rhea (Web Wallet)
Milestone
No milestone
Development

No branches or pull requests
2 participants
@erwanor @aubrika