Learn • Solana • High-throughput non-EVM network

Token Approvals Explained on Solana

Why token approvals matter, what they authorize, and how to review them responsibly.

Why this matters on Solana

An approval gives a contract permission to spend a specified token balance under the rules of that approval. Reviewing old approvals can reduce exposure to applications you no longer use.

Solana uses a different account and token model from EVM networks, so EVM assumptions should not be applied directly.

Solana does not follow standard EVM conventions. Address formats, token identifiers and approval mechanics differ, so EVM-oriented checklists and tools should only be applied to Solana after confirming they are supported.

Solana: what to pay attention to

  • Security: Use trusted wallet interfaces and review transaction effects before approving them.
  • Assets and tokens: Verify the mint address and relevant token-account details rather than relying on ticker symbols.
  • Costs: Consider transaction costs and token-account mechanics when evaluating small balances.

A Solana checklist for this topic

  • Treat unexpected tokens or links that appear in a Solana wallet as untrusted until verified.
  • Review and revoke permissions you no longer use on Solana, especially unlimited approvals.
  • Check the domain you are on before connecting a wallet for any Solana action.
  • Send a small test amount first when an address or route on Solana is new to you.
A signature is a decision. If a request cannot be explained in plain words, it is not ready to be signed.

Bridge from Solana

Consider transaction costs and token-account mechanics when evaluating small balances. On the zkSync side: verify the asset contract on zkSync before assuming it matches another network.

The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.

Solana → zkSync BRIDGE GUIDE

Related guides