Fix burn and renounced filters #124
Open
Conversation
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
|
@TheoBrigitte I tried the the fix but it looks like it is not working. 8pUmSNVM37u1nncneC3MWsfge3edqZc9JJ1zJ4TuvE6d This mint has freeze disabled but the bot said that Creator can freeze tokens and skipped it. RenouncedFreeze -> Creator can freeze tokens Is there a possibility that the initially the token did not have freeze disabled or there is something wrong in the logic? |
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.
Fixing the burn filter by removing the check for error -32602. Otherwise this filter catches non-burned token.
Fixing the freeze filter by checking if the freezeAuthority address is either null or set to to a null address. Otherwise this filter catches freezable tokens.
Also fixes an issue where setting renounce to true and freezable to false would reject every token.