-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
tm v0.37.0-rc2, sdk 0.47.0-rc1, and ibc-go v7 #1068
Conversation
This is ready for review, but currently using https://github.com/strangelove-ventures/ibc-go/tree/andrew/47-rc1 as a replace ibc-go dependency. This should not be merged until we are pointed to an ibc-go commit on the upstream repo. EDIT: updated to ibc-go v7 from main on 01/29/2023. e2e test case for the decoding version boundary here strangelove-ventures/interchaintest#359 |
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.
Had a few comments but otherwise this looks good!!
…nges for sdk 0.47, tm 0.37, ibc-go v6
bd6307a
to
7a37b60
Compare
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.
Ahh blanked on the buf.yaml files last time, good catch! This looks good to go now and this should close #737
Those weren't needed actually until pulling in main with the stride changes that introduced
|
Detect tendermint version from nodes for conditional on decoding. When tendermint version is lower than
v0.37-alpha
, events are base64 encoded and need to be decoded first. Since calls to nodeStatus
are already done to get the latest height, and this response includes the tendermint version, we can keep the flag up to date at runtime. This allows a seamless transition for the relayer when a chain upgrades across the tm v0.37 boundary, the relayer will detect the new version and not need a restart.ibcexported.Header
is nowibcexported.ClientMessage
Resolves #737