Token 2022 extensions are optional features attached to a mint or a token account under the Token-2022 program. For a decoder they fall into four groups: extensions that change what an amount means, one that adds an extra program call, ones that change who may move tokens, and metadata that changes nothing about transfers. Check the mint before trusting amounts.
Program ID and compatibility#
Token-2022 lives at TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb, separate from SPL Token. Its base instructions use the same tags and layouts as SPL Token's instructions, so a transfer decoder works on both if it checks the program ID. Extensions add data to mint and token accounts, and some add instructions of their own under extra tags.
A transaction does not say which extensions a mint has. You learn that from the mint account, which is outside what raw shreds carry.
Every extension, sorted by what it does to decoding#
| Effect on a decoder | Extensions |
|---|---|
| Changes the amount you should report | TransferFeeConfig and TransferFeeAmount; ConfidentialTransferMint, ConfidentialTransferAccount and the confidential fee and mint-burn extensions; InterestBearingConfig; ScaledUiAmount |
| Adds an extra program call | TransferHook and TransferHookAccount |
| Changes who may move tokens, not the amounts | PermanentDelegate, DefaultAccountState, NonTransferable, NonTransferableAccount, Pausable, PausableAccount, CpiGuard, MemoTransfer, PermissionedBurn |
| Metadata or housekeeping only | MetadataPointer, TokenMetadata, GroupPointer, TokenGroup, GroupMemberPointer, TokenGroupMember, MintCloseAuthority, ImmutableOwner |
The list is the program's own ExtensionType enum at commit 875693f; test-only types are left out.
Extensions that change amounts#
Transfer fees. A mint with a transfer fee keeps part of each transfer in the recipient's account as withheld fees. The amount in the instruction is what left the sender; the recipient's usable balance grows by less. The fee-aware transfer instruction states the expected fee alongside the amount, so a decoder can report both.
Confidential transfers. Amounts in confidential transfers are encrypted. A decoder can see that a transfer happened between two accounts, not how much moved.
Interest-bearing and scaled amounts. These change how a raw amount is displayed, not the raw amount itself. The instruction's integer is still correct; converting it to a human figure needs the mint's current configuration, not only its decimals.
Transfer hooks#
A mint with a transfer hook names a hook program that Token-2022 calls on every transfer, passing extra accounts listed in an account owned by the hook. For a decoder that means two things: transfers of these tokens carry more accounts than usual, and they trigger a program call of their own. That call is an inner instruction, so it appears only in execution data.
Metadata extensions#
MetadataPointer and TokenMetadata let a mint carry its name, symbol and URI on chain, in the mint account itself. They make no difference to how transfers decode. They do make Token-2022 mints self-describing, which is why so many new tokens use them.
What real mints use#
The 94 Token-2022 mints that appeared in two consecutive mainnet blocks on 18 November 2026, read back from chain (91 were readable), carried these extensions:
| Extension | Mints |
|---|---|
| MetadataPointer and TokenMetadata | 90 |
| TransferFeeConfig | 5 |
| TransferHook | 3 |
| ConfidentialTransferMint | 2 |
| PermanentDelegate | 2 |
| DefaultAccountState | 2 |
| ScaledUiAmount | 1 |
| Pausable | 1 |
| MintCloseAuthority | 1 |
Most Token-2022 tokens in that sample are metadata-only and decode like SPL Token. A few, the ones with fees, hooks or confidential balances, need the special handling above.
Token-2022 from shreds#
From shreds you see the instruction, with its amount and accounts, but not the mint's configuration. Keep a cache of mint extensions, filled from the mint account the first time you meet a mint, and refresh it occasionally: some settings, such as transfer fees, can be updated by their authority. Then decode amounts with the extensions in mind. The associated token accounts page covers the token accounts these transfers move between.
Questions about Token-2022 extensions#
Do Token-2022 transfers decode like SPL Token transfers?#
The base instructions use the same tags and layouts, so yes, provided you check which program the instruction calls.
Can I read the amount of a confidential transfer?#
No. The amount is encrypted; you can see the accounts involved, not the value.
Does a transfer fee change the amount in the instruction?#
No. The instruction states what the sender sends; the fee is withheld from what the recipient receives.
What a transaction alone will not tell you#
Whether a mint has extensions, what its fee rate is and which hook it calls all live in account data, not in the transaction. The amount withheld, the hook's effects and the final balances are execution results. A shred decoder that ignores mint state will report fee-bearing and confidential transfers wrongly, and Token-2022 surprises collects the common cases.
Decoding Token-2022 in practice#
The Token-2022 recipe decodes its transfers in code, and the SPL Token transfer recipe covers the shared base layout. To meet Token-2022 tokens in live traffic, decode a first transaction from raw shreds.
Sources#
- solana-program/token-2022 interface/src/extension/mod.rs, commit 875693f: ExtensionType (checked 2026-11-18)
- Token-2022 extension guide (checked 2026-11-18)
- Mainnet getMultipleAccounts (jsonParsed) for the 94 Token-2022 mints in slots 470,901,815 and 470,901,816 (checked 2026-11-18)
Raw shreds on your own server
Ultra Low Latency Shreds is $200 and Standard Shreds is $100. You pay in crypto, tell us which IPv4 address and UDP port should receive the stream, and we wire it up by hand.