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
There needs to be an event specification to improve interoperability between IBC implementations from the relayer point of view. Not sure if this has already been opened as an issue, but thought I'd open one just in case it hasn't.
It'd be good to prioritize this discussion since the event system currently being used in the SDK/Tendermint combo is sub-par and there is active discussion in how to refactor it. Events are a core component of IBC functioning, almost like pipes in a building, and we should ensure they are stable and well designed.
The initial idea for typed events sounds good, but it seems to be a little hacky in practice. Things I'm unsure of:
does the event spec use the ABCI format to specify events?
are we defining the events as proto types?
should we define event system requirements (and does the SDK meet these requirements)?
The text was updated successfully, but these errors were encountered:
There needs to be an event specification to improve interoperability between IBC implementations from the relayer point of view. Not sure if this has already been opened as an issue, but thought I'd open one just in case it hasn't.
It'd be good to prioritize this discussion since the event system currently being used in the SDK/Tendermint combo is sub-par and there is active discussion in how to refactor it. Events are a core component of IBC functioning, almost like pipes in a building, and we should ensure they are stable and well designed.
The initial idea for typed events sounds good, but it seems to be a little hacky in practice. Things I'm unsure of:
The text was updated successfully, but these errors were encountered: