Token-2022

Overview

What it means in plain English

Token-2022 is Solana’s newer token program, also presented as Token Extensions, providing optional native features beyond the original SPL Token Program. Mints and token accounts can enable extensions such as transfer fees, transfer hooks, metadata pointers, interest, confidential transfers, default states, and permanent delegates. Token-2022 uses a different program ID from the original Token Program, and not every wallet, exchange, protocol, or extension combination is supported.

How it works and why it matters

Token-2022 is Solana’s newer token program, also presented as Token Extensions, providing optional native features beyond the original SPL Token Program.

Mints and token accounts can enable extensions such as transfer fees, transfer hooks, metadata pointers, interest, confidential transfers, default states, and permanent delegates. Token-2022 defines an interface or data model that compatible contracts, programs, wallets, and applications can recognize. A standard can specify functions, events, account layouts, metadata, permissions, or extension behavior, but each implementation can still add custom logic.

Token-2022 uses a different program ID from the original Token Program, and not every wallet, exchange, protocol, or extension combination is supported. Interfaces should use feature detection and official contract identifiers rather than infer support from a symbol.

Risks include incompatible extensions, hidden authorities, account-size requirements, transfer-hook failure, fee behavior, unsupported deposits, and incorrect program assumptions. Risks include nonstandard return values, callback reentrancy, malicious extensions, transfer fees, paused or restricted transfers, upgrade authority, incorrect decimals, duplicate metadata, and wallets that ignore optional behavior.

Applications should verify mint, token program, enabled extensions, authorities, account size, transfer effects, extension compatibility, wallet support, and official program ID. Payment systems should allowlist network-contract pairs and reject tokens that merely reuse a familiar symbol. Token behavior such as fees, rebasing, blacklisting, or transfer hooks must be included in amount matching and refund logic.

Integrators should enable only the extensions they have explicitly tested and can monitor in production.

Extension data should be read from the mint and token accounts because transfer fees, hooks, confidential transfers, or permanent delegates can change ordinary SPL-token assumptions.

Worked example

A Solana project issues a token using the Token Extensions Program rather than the older SPL Token Program. The asset may support extra rules such as transfer fees, transfer hooks or confidential transfers. A payment processor that assumes every Solana token behaves identically may miscount funds.

Practical checks and common confusion

A token's program ID and enabled extensions can change transfer mechanics. Verify actual recipient balance deltas, fee handling and compatible wallet software. The ticker alone does not reveal whether transfers are unrestricted or whether additional accounts are required.

Learn the related concepts

Asset-Referenced Token (ART) Wrapped Bitcoin (WBTC)

Primary documentation

Solana Token-2022 Program Guide.