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

Add thorough IBC upgrade documentation #7877

Closed
4 tasks
colin-axner opened this issue Nov 10, 2020 · 1 comment · Fixed by #8298
Closed
4 tasks

Add thorough IBC upgrade documentation #7877

colin-axner opened this issue Nov 10, 2020 · 1 comment · Fixed by #8298
Labels
T:Docs Changes and features related to documentation.

Comments

@colin-axner
Copy link
Contributor

colin-axner commented Nov 10, 2020

Summary

Upgrading or updating a client via a governance proposal requires a lot of consideration. We should add thorough documentation to cover all cases. For example, allowing a client to be unexpired leads to a more flexible header being used to update a client. Furthermore, unfreezing a client needs to take into consideration that if the misbehaviour isn't expired by the time the client unfreezes than the client can be unfrozen again.

EDIT Splitting Upgrade and UpdateProposalDocumentation into separate issues.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@colin-axner colin-axner added T:Docs Changes and features related to documentation. x/ibc labels Nov 10, 2020
@colin-axner
Copy link
Contributor Author

Also document exactly what TrustLevel is doing

@AdityaSripal AdityaSripal changed the title Add thorough IBC upgrade and proposal update documentation Add thorough IBC upgrade documentation Jan 11, 2021
@mergify mergify bot closed this as completed in #8298 Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T:Docs Changes and features related to documentation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant