Fix: Incorrect event emission in burnFrom()#31
Merged
mudgen merged 1 commit intoPerfect-Abstractions:mainfrom Oct 21, 2025
Merged
Fix: Incorrect event emission in burnFrom()#31mudgen merged 1 commit intoPerfect-Abstractions:mainfrom
mudgen merged 1 commit intoPerfect-Abstractions:mainfrom
Conversation
The burnFrom() function was emitting a Transfer event with msg.sender as the 'from' address instead of _account (the address whose tokens are being burned). This caused event logs to incorrectly report who the tokens were burned from, breaking compatibility with wallets and indexers that rely on Transfer events.
JackieXu
pushed a commit
to JackieXu/Compose
that referenced
this pull request
Nov 6, 2025
…-event Fix: Incorrect event emission in burnFrom()
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #25
The burnFrom() function was emitting a Transfer event with msg.sender as the 'from' address instead of _account (the address whose tokens are being burned).
This caused event logs to incorrectly report who the tokens were burned from, breaking compatibility with wallets and indexers that rely on Transfer events.