fix tron parser of internal Tx for only native token #37
Conversation
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
Author
|
bugbot run |
PikaZ76
force-pushed
the
fix/TronNativeTokenInInternalTx
branch
from
8bbaf10 to
a3d85a5
Compare
PikaZ76
force-pushed
the
fix/TronNativeTokenInInternalTx
branch
from
a3d85a5 to
ab92867
Compare
zhanwu
approved these changes
Jun 18, 2025
|
bugbot run |
aegis-cipherowl
approved these changes
Jun 18, 2025
OriZhai
approved these changes
Jun 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed? Why?
to fix bug for native and TRC10 tokens parser in InternalTx. only keep native token.
ValueCallValueInfoto store origin data in protoHow did you test the change?