-
Notifications
You must be signed in to change notification settings - Fork 75
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(sequencer): move fee event recording to tx level (#1718)
## Summary Moves ABCI fee events to `FinalizeBlock.tx_results` to identify fees on a per transaction basis. ## Background Post-fee rework, fee ABCI event construction was happening outside of transaction execution and (wrongly) included in the `FinalizeBlock.events` field of the finalize block response. This made it difficult to identify which fee events were related to which transaction. This patch moves fee event construction back into the (atomic) transaction execution, so that the generated ABCI fee events per transaction are again part of `FinalizeBlock.tx_results`. For example for Astrotek fees will again show up next to each transaction. ## Changes - Moved fee event construction back into transaction execution. ## Testing Adjusted fee event unit test to ensure fee event is returned as part of transaction execution.
- Loading branch information
1 parent
94a63d7
commit 1df9031
Showing
4 changed files
with
30 additions
and
57 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters