Support for SPL Token 2022 Transfers and Visibility #8
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
📝 Summary
This PR adds support for SPL Token 2022 transfers in the Squads v3 client. Previously, the client only supported standard SPL tokens (minted under the original Token Program), and would throw errors when interacting with newer SPL Token 2022 tokens.
🔧 What’s New?
🚀 Why?
Since the Squads v3 web client does not currently support SPL Token 2022, users are unable to interact with Token 2022 mints directly through the standard Squads web interface. This PR adds support for Token 2022 transfers within the client, giving users a way to interact with Token 2022 tokens via this client if needed.
🧪 Testing
🔍 Notes