-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
fix: emit ante events even for the failed txs #10631
fix: emit ante events even for the failed txs #10631
Conversation
c7125ad
to
4e04904
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.
Thanks @YunSuk-Yeo, this PR makes sense to me.
The behavior is correct on master, right?
I'm not sure, master still have this problem. but v0.44.x should have this update for rosetta support |
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.
lgtm
This change is consensus-breaking because of the tx result change right? |
I don't think emitting new events is considered as consensus-breaking |
correct events are not included in hashes in the header |
* emit ante events even for the failed txs * apply comment * add changelog
* emit ante events even for the failed txs * apply comment * add changelog
* emit ante events even for the failed txs * apply comment * add changelog
Description
Closes: #10618
This is example implementation to emit ante events(especially of tx fee deduction) for the failed txs.
The master branch has huge difference in ante handler side (changed to middleware), so I just made changes only for v0.44.x branch.
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change