Figure out common format for IBC events #31
Comments
|
What does it take to achieve these? Are we coordinating with the SDK team on what this would look like? Is there an open issue there for this that we can link? In the meantime I think we can bump the milestone |
|
I think this is some relevant work from the SDK team cosmos/cosmos-sdk#7406, which is being reworked at the moment. We should align with them once the refactored ADR 031 kicks in. |
9 tasks
|
Linking a new issues from the spec repo related to this https://github.com/cosmos/ics/issues/512 |
livelybug
referenced
this issue
in octopus-network/ibc-rs
Oct 14, 2022
Closes: #30 Query of client consensus now distinguishes between query height and consensus height. Specifically: - `chain_height` is the height at which the query is made (can be 0 if the latest state on chain is queried). - `consensus_height` is the consensus height of the client running on this chain but it represents a height of the client's chain and should be used to construct the query path.
|
There is now an issue on the spec repo; we should continue the discussion there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tendermint currently outputs IBC events as bulk of strings. This leads to lot of manual and potentially error prone code on the relayer side.
Ideally IBC events are defined using Protobuf and Tendermint should emits it using this format. This eliminates lot of boilerplate and error prone code on the relayer side.
The text was updated successfully, but these errors were encountered: