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

ICS ?: IBC threat model & security assumptions #2

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

ICS ?: IBC threat model & security assumptions #2

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

Comments

@cwgoes
Copy link
Contributor

cwgoes commented Feb 11, 2019

Primarily a port of the original IBC spec.

Will cover:

  • Security assumptions of the underlying consensus
  • Required slashing conditions / evidence handling
  • Exceptional cases and possible 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
Copy link
Contributor Author

cwgoes commented Mar 5, 2019

Could possibly be merged into #25, not sure if these are sufficiently distinct to warrant separate specs.

@mossid
Copy link

mossid commented Mar 5, 2019

I think Security assumption can be merged into #25, Exceptional cases and recovery methods can be merged into #6, and slashing conditions / evidence handling can be merged into #10 and separated into a new issue, perhaps validator remote slashing on Application layer section.

@cwgoes
Copy link
Contributor Author

cwgoes commented Mar 5, 2019

I think Security assumption can be merged into #25, Exceptional cases and recovery methods can be merged into #6, and slashing conditions / evidence handling can be merged into #10 and separated into a new issue, perhaps validator remote slashing on Application layer section.

Perfect, done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tao Transport, authentication, & ordering layer.
Projects
None yet
Development

No branches or pull requests

2 participants