-
Notifications
You must be signed in to change notification settings - Fork 383
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
ICS 18: specifying events emitted by core IBC #981
base: main
Are you sure you want to change the base?
ICS 18: specifying events emitted by core IBC #981
Conversation
Great initiative |
IBC that relayers need to use to complete client, connection and channel lifecycles, relay and | ||
timeout packets. | ||
|
||
Events emitted by core IBC are JSON-encoded objects following the schema: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are events JSON-encoded, rather than proto-encoded like other IBC data?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cosmos/ibc-go#54 but can't really speak on if/when this will be included.
"key": "counterparty_connection_id", | ||
"value": "{counterparty.connectionId}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be removed. It is blank here and autogenerated on TRY
"key": "counterparty_channel_id", | ||
"value": "{counterparty.channelId}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be removed since it is just blank and autogenerated on TRY
}, | ||
{ | ||
"key": "connection_id", | ||
"value": "{connectionHops[0]}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note this will need to change for multihop. Perhaps we can create a tracking issue
closes: #606