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

[ICS24] Include “IterateConsensusStates” key #1090

Closed
Farhad-Shabani opened this issue Feb 15, 2024 · 0 comments · Fixed by #1091
Closed

[ICS24] Include “IterateConsensusStates” key #1090

Farhad-Shabani opened this issue Feb 15, 2024 · 0 comments · Fixed by #1091
Assignees
Labels
O: usability Objective: aims to enhance user experience (UX) and streamline product usability
Milestone

Comments

@Farhad-Shabani
Copy link
Member

Farhad-Shabani commented Feb 15, 2024

Feature Summary

ibc-go records consensus state update heights using a specific iteration key with the key formatted as: iterateConsensusStates{BigEndianRevisionBytes}{BigEndianHeightBytes}

The definition of this iteration key can be added under ICS24 to simplify the lives of CosmWasm client developers and ensure cross-compatibility with ibc-go.

@Farhad-Shabani Farhad-Shabani added the O: usability Objective: aims to enhance user experience (UX) and streamline product usability label Feb 15, 2024
@Farhad-Shabani Farhad-Shabani added this to the 0.51.0 milestone Feb 15, 2024
@Farhad-Shabani Farhad-Shabani self-assigned this Feb 15, 2024
@github-project-automation github-project-automation bot moved this to 📥 To Do in ibc-rs Feb 15, 2024
@Farhad-Shabani Farhad-Shabani changed the title [ICS24] Include “IterateConsensusStates” path [ICS24] Include “IterateConsensusStates” key Feb 15, 2024
@github-project-automation github-project-automation bot moved this from 📥 To Do to ✅ Done in ibc-rs Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O: usability Objective: aims to enhance user experience (UX) and streamline product usability
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant