Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Remove ServiceMsgs from ADR-031 #9139
Remove ServiceMsgs from ADR-031 #9139
Changes from 33 commits
f1398cb
b54d71f
03a358d
2a6223e
559fc54
f2d8355
d5c6ce9
569f777
19720e7
c52587c
aa30868
2919375
488dc62
72c0cbc
04ba707
5f543a4
6d1b1cc
16b72f1
d4130c2
5f4a19c
d5a2982
9743b9e
a323bff
14acc84
0e57b6f
0840c18
5cb4301
fc37733
5d1836b
fcaedf9
7904aef
b2bf609
77e20c2
3cac0e6
113ef64
1c3886d
09e81a2
7e05b80
68b7e5f
bb33c2b
c2a024d
f25b2c6
31e5c2a
d6ab3eb
3e7d3ae
2000ebf
a688c73
666fe92
aa2b26c
249f857
d2a8ae5
cd4bc02
774a4ab
d3c3381
98ad2b7
e95ae32
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The
message.action
is very important for relayers as it is used to distinguish when the next message event starts/ends and what type of event is occurring. Relayers may be connected to chains on the old version and the new version and thus need to be aware of this change to ensure IBC continues to work between chains with different versionsDoes the
svcMsg.MethodName
!=sdk.MsgTypeURL(msg)
? Or is there no breaking change here for Msgs migrated to proto messages registered on a Msg service (which from my understanding is the case for the current IBC Msgs). I'm a little fuzzy on the exact differences between the legacy messages, the proto message req/resp types and the msg service router, so please excuse me if I used the terminology wrongThere 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.
It's just confusing, to me too. I tried to simplify it like this:
In v0.42, these message.actions were emitted:
message.action='/cosmos.bank.v1beta1.Msg/Send'
if the user explicity sent aServiceMsg
tx (note the 2/
)message.action='send'
for all other messages (99% of the messages)After this PR:
message.action='/cosmos.bank.v1beta1.MsgSend'
(note only 1/
), so legacymessage.action='send'
are not emitted anymore (unless the app developer didn't wire up proto registration correctly). This is not retroactive though.Let me know if that works for IBC.
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.
I see, thanks for the response! This makes sense. This should be fine for relayers, but it will likely require a small change. Relayer should now check for
message.action='send' || message.action='/cosmos.bank.v1beta1.MsgSend'
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.
Yes, that's the approach I'm taking too, e.g. if querying deposits here.
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.
type URL right?
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.
Yes, changed! See #9139 (comment) for reason.
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.
is there context available in
sd
? We should use it instead of context.BackgroundThere 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.
Unfortunately not, sd is just a descriptor.
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 we don't return an error?
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.
If we return an error, then the app will continue running, with potential encoding errors that are hard to debug down the road.
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.
whenever I see it I always read FAQ method 🤣