You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
process() function in connection and channel handlers should follow the same approach as the one in client wrt identifier allocation, i.e. the process() function should return an ID that is later stored by the keeper that also increments the next identifier to be available for next handler calls.
Problem Definition
Proposal
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate milestone (priority) applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
romac
changed the title
consistent identifier handling across client, connections and channels
Consistent identifier handling across client, connections and channels
Feb 9, 2021
* (#91) WIP: Added validation for ICS7 ClientState::new().
* Bit more progress on validation for ICS7 ClientState::new()
* Initialization for dummy header done. Tests done.
* Added the JSON representation of a dummy signed header.
livelybug
pushed a commit
to octopus-network/ibc-rs
that referenced
this issue
Oct 14, 2022
* (cosmos#91) WIP: Added validation for ICS7 ClientState::new().
* Bit more progress on validation for ICS7 ClientState::new()
* Initialization for dummy header done. Tests done.
* Added the JSON representation of a dummy signed header.
Crate
modules
Summary
process()
function in connection and channel handlers should follow the same approach as the one in client wrt identifier allocation, i.e. theprocess()
function should return an ID that is later stored by the keeper that also increments the next identifier to be available for next handler calls.Problem Definition
Proposal
For Admin Use
The text was updated successfully, but these errors were encountered: