fix: handle anonymous events in encodeEventTopics#4576
Closed
tenderdeve wants to merge 1 commit into
Closed
Conversation
Anonymous events should not have their signature prepended as topic[0]. Previously, encodeEventTopics unconditionally added the event signature as the first topic, which is incorrect for anonymous events per the Solidity ABI spec. Fixes wevm#4461
|
@tenderdeve is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
|
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.
encodeEventTopics unconditionally prepended the event signature as topic[0], which is incorrect for anonymous events. Anonymous events have no signature topic per the Solidity ABI spec, so all 4 topic slots are available for indexed parameters.
This skips the signature when
abiItem.anonymousis true and widens the return type accordingly.Fixes #4461