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 12: IBC Byzantine recovery strategies #6

Closed
cwgoes opened this issue Feb 11, 2019 · 4 comments
Closed

ICS 12: IBC Byzantine recovery strategies #6

cwgoes opened this issue Feb 11, 2019 · 4 comments
Labels
tao Transport, authentication, & ordering layer.

Comments

@cwgoes
Copy link
Contributor

cwgoes commented Feb 11, 2019 •
edited

Primarily a port of the appendix in the original IBC spec - pretty speculative for now.

Will cover:

  • Definitions of Byzantine events
  • IBC-layer strategies for recovering from Byzantine events
  • Application-layer strategies from recovering from Byzantine events
  • Exception cases and recovery methods
@cwgoes cwgoes added tao Transport, authentication, & ordering layer. stage-strawman labels Feb 11, 2019
@cwgoes cwgoes self-assigned this Mar 5, 2019
@cwgoes cwgoes mentioned this issue Mar 5, 2019
Closed
6 tasks
@mossid mossid mentioned this issue Mar 5, 2019
Closed
@cwgoes cwgoes changed the title ICS ?: IBC Byzantine recovery strategies ICS 12: IBC Byzantine recovery strategies Mar 5, 2019
This was referenced Mar 26, 2019
Closed
Merged
@cwgoes cwgoes mentioned this issue Apr 1, 2019
Closed
@cwgoes cwgoes mentioned this issue Apr 23, 2019
Merged
@cwgoes
Copy link
Contributor Author

cwgoes commented Apr 23, 2019

Ref #70 (comment)

@cwgoes cwgoes mentioned this issue May 13, 2019
Closed
@cwgoes
Copy link
Contributor Author

cwgoes commented Jun 8, 2019

How about modules can check if a client has been frozen and take action accordingly?

It isn't synchronous though...

@cwgoes cwgoes removed their assignment Jun 29, 2019
@cwgoes
Copy link
Contributor Author

cwgoes commented Jun 29, 2019

This is relatively low-priority, and will likely need to discuss application-specific methods for e.g. value transfer (limiting throughput per unit time) and pegzones (varying confirmation levels for varying risk).

@cwgoes
Copy link
Contributor Author

cwgoes commented Aug 17, 2019

The validity predicate in ICS 2 has become sufficiently general that it encapsulates this.

We should still discuss specific cases therein.

@cwgoes cwgoes closed this as completed Aug 17, 2019
en pushed a commit to en/ics that referenced this issue Dec 14, 2019
@gitlocalize-app @en
Translate README.md via GitLocalize (cosmos#6)
629d360
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
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cwgoes