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

ICS ?: Liveness Violation Recovery #63

Closed
mossid opened this issue Apr 1, 2019 · 3 comments
Closed

ICS ?: Liveness Violation Recovery #63

mossid opened this issue Apr 1, 2019 · 3 comments
Labels
tao Transport, authentication, & ordering layer.

Comments

@mossid
Copy link

mossid commented Apr 1, 2019

When a chain does not (or expected to not) produces block anymore(e.g. incompatible hard fork including 1/2 < vals < 2/3 fork, synchronized halt, etc.), then any packet(not datagram) sent to the chain after the event happened will be lost. A manual procedure to disconnect the connection and possibly recover the connection to the new chain is needed.
@mossid mossid added tao Transport, authentication, & ordering layer. stage-strawman labels Apr 1, 2019
@mossid mossid mentioned this issue Apr 1, 2019
Merged
@cwgoes
Copy link
Contributor

cwgoes commented Apr 1, 2019

I think this falls within #6.

@cwgoes
Copy link
Contributor

cwgoes commented Oct 17, 2019

Is there a specific spec you want to write for this @mossid?

I think our present client abstraction may be sufficiently generic.

@cwgoes
Copy link
Contributor

cwgoes commented Sep 8, 2020

This has been done in the SDK (governance override option for clients).

@cwgoes cwgoes closed this as completed Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tao Transport, authentication, & ordering layer.
Projects
IBC-GO Eureka
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mossid @cwgoes