fix: Use destination wallet input when minting ABL tokens#580
Open
fix: Use destination wallet input when minting ABL tokens#580
Conversation
The mint flow was ignoring the Destination Wallet field and always minting to the connected wallet's ATA. Read the input value and fall back to the connected wallet only when empty.
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
1 participant
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.
The Mint New Tokens form in the ABL token manage page captured the Destination Wallet input into state but never passed it to the mint mutation, so tokens always landed in the connected wallet's ATA regardless of what was typed.
Now
handleMintreadsdestinationWallet, parses it as aPublicKey, and uses it as therecipient. If the field is empty it falls back to the connected wallet so the previous default behavior still works.