feat: add FeeOnTransfer to ContractInfoExtension - #35
Merged
Merged
Conversation
ScreamingHawk
marked this pull request as ready for review
August 21, 2026 02:33
miguelmota
approved these changes
Aug 21, 2026
Member
|
LGTM |
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.
Adds
FeeOnTransfer booltoContractInfoExtension, matching theextensions.feeOnTransferfield introduced by 0xsequence/token-directory#153.Fee-on-transfer tokens deduct a tax on transfer, so the recipient receives less than the sender sent. This exposes the flag to Go consumers so they can act on it (e.g. surface it in token listings or reject exact-amount flows).