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

[ICS02] Implement IBC client recovery mechanisms #738

Closed
4 tasks done
Tracked by #554
Farhad-Shabani opened this issue Jun 30, 2023 · 3 comments
Closed
4 tasks done
Tracked by #554

[ICS02] Implement IBC client recovery mechanisms #738

Farhad-Shabani opened this issue Jun 30, 2023 · 3 comments
Assignees
Labels
A: critical Admin: critical or Important O: reliability Objective: cause to improve trustworthiness and consistent performing

Comments

@Farhad-Shabani
Copy link
Member

Farhad-Shabani commented Jun 30, 2023

Problem Statement

If a client gets frozen or expired it can no longer be updated, the associated connection(s) and channel(s) will also stop working and funds in the channels will be permanently locked and not transferrable.

ibc-rs needs a mechanism by which frozen IBC clients can be recovered. This functionality has been implemented in ibc-go as part of ADR 026. We'll need to implement similar functionality in ibc-rs in order to maintain feature parity.

@rnbguy
Copy link
Collaborator

rnbguy commented Apr 8, 2024

All the tasks are finished. Does that make this tracking issue finished too?

@Farhad-Shabani
Copy link
Member Author

I think @seanchen1991 is addressing the final aspect of this feature in informalsystems/basecoin-rs#173 to ensure its functionality. Once that's completed, we can consider closing this issue.

@rnbguy
Copy link
Collaborator

rnbguy commented May 23, 2024

@seanchen1991 we can close this now, right?

@github-project-automation github-project-automation bot moved this from 📥 To Do to ✅ Done in ibc-rs May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: critical Admin: critical or Important O: reliability Objective: cause to improve trustworthiness and consistent performing
Projects
Status: Done
Development

No branches or pull requests

3 participants