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
Is your feature request related to a problem? Please describe.
One of the issues we ran into while debugging compatibility between pd and rly was inconsistent encoding of event data that was intended to be picked up by the relayer. Currently, we handle events with events::named_event(...) -> Event constructors that take typed values and create events from them. However, this is still somewhat error-prone.
Describe the solution you'd like
After informalsystems/tendermint-rs#1288 lands upstream, we can define our own domain types representing the data in abci::Events. This will give us a more maintainable, single source of truth on how our event serialization should be defined.
The text was updated successfully, but these errors were encountered:
Instead of changing the types in our penumbra-ibc crate, we should try to align with the ibc-types refactoring. In other words, this should be part of the ibc-types refactoring.
Is your feature request related to a problem? Please describe.
One of the issues we ran into while debugging compatibility between
pd
andrly
was inconsistent encoding of event data that was intended to be picked up by the relayer. Currently, we handle events withevents::named_event(...) -> Event
constructors that take typed values and create events from them. However, this is still somewhat error-prone.Describe the solution you'd like
After informalsystems/tendermint-rs#1288 lands upstream, we can define our own domain types representing the data in
abci::Event
s. This will give us a more maintainable, single source of truth on how our event serialization should be defined.The text was updated successfully, but these errors were encountered: