Integrate basic token-2022 support #311
Merged
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
|
@joncinque is attempting to deploy a commit to the Solana Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
mcintyre94
approved these changes
Dec 15, 2023
|
Yeah for sure! The emphasis for this PR should be on the word "basic" 😅 |
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.
Problem
Token-2022 has been around for awhile, but the explorer still has no knowledge of it!
Summary of changes
This is really just basic support, and it was done in a pretty simple manner:
"spl-token", which is the program name returned from JSON-parsed encoding, and make sure that it also supports"spl-token-2022"TOKEN_PROGRAM_ID, and make sure that it also supportsTOKEN_2022_PROGRAM_IDSo in the end, accounts and mints are properly displayed, and the additional token-2022 accounts are fetched too.
There is no parsing of extensions included in this PR, but it can certainly be done in follow-up work.