Solana Token-2022 Freeze vs Clawback for Wallet Ops

Solana wallets do not have one freeze switch. They have token accounts, mint-level authorities, and — on Token-2022 — extra extensions that can move balances without the holder’s signature. Desks that copy an Ethereum isBlackListed script into a Solana ticket will mis-route the case. This post is the wallet-ops layer: freeze versus clawback, what Solana’s own docs actually say, and how that differs from FreezeRadar’s registered Solana USDC/USDT path. It does not replace the search landing Solana USDC freeze check or the glossary owner freeze authority.

Educational only. Not legal advice. Not a bypass for issuer, mint, or lawful-order controls. Not a walkthrough for exercising freeze or permanent-delegate keys.

Direct answer

On Solana, freeze is a mint authority that sets a token account to frozen. Official Solana docs for FreezeAccount say a frozen token account keeps the same owner, mint, and balance, but cannot receive, transfer, or burn until it is thawed. Token-2022 adds a separate extension, permanent delegate: a mint-level key that can authorize transfers and burns for any token account of that mint, and holders cannot revoke it. Freeze locks; permanent delegate can take. Circle-issued USDC on Solana is still a classic SPL freeze-authority product in FreezeRadar’s registry. Arbitrary Token-2022 RWAs are not FreezeRadar scan assets. Read the mint on an explorer before you treat a “frozen Solana wallet” ticket as USDC.

Who owns which query

Question	Owner page
Screen a Solana USDC wallet before transfer	Guide landing: Solana USDC freeze check
What “freeze authority” means across chains	Glossary: freeze authority
Token-2022 freeze vs permanent-delegate clawback for wallet ops	This post
USDT vs USDC desk dialects, including Solana USDC	USDT vs USDC desk view

Do not publish a competing thin /guides landing for Token-2022. The USDC query stays on the existing Solana USDC page.

Two programs, two stories

Classic SPL Token. The mint stores an optional freeze_authority. If it is set, that key can freeze or thaw token accounts. If it is None, nobody can freeze that mint later. FreezeRadar already treats a frozen SPL token-account state for registered USDC and USDT as a direct signal. Absence of frozen is not a prediction that Circle or Tether will never act.

Token-2022 (Token Extension Program). Same freeze/thaw instructions exist, plus extensions. The ones that change desk language:

• Freeze authority — same job as classic SPL, on the Token-2022 program id.
• Permanent delegate — Solana’s docs: a mint-level authority that can authorize transfers and burns for any token account for that mint. It acts as a global delegate. Token-account owners cannot revoke it. The mint authority can rotate it with SetAuthority / AuthorityType::PermanentDelegate.
• Default account state — new token accounts can start frozen so a service must thaw them before they are usable.

A ticket that says “Solana froze my wallet” is incomplete until you name the mint, the token account, the program (Token vs Token-2022), and which authority fired.

Freeze is not clawback

Keep these in separate columns on the runbook.

Control	What it does	What it does not do
Freeze / thaw	Sets account state; Solana docs: no receive, transfer, or burn until thawed	Does not, by itself, empty the account
Permanent delegate	Can transfer or burn from any account of that mint without the holder’s consent	Is not the same instruction as FreezeAccount
Close account	Can close a zero-balance frozen account per Solana freeze docs	Does not recover a non-zero frozen balance

If ops writes “clawback” in a USDC ticket because they saw a Token-2022 explainer, you have already confused Circle’s freeze authority with someone else’s permanent delegate.

Solana’s Token-2022 extension guide also notes a confidential-balance caveat: permanent delegate does not work against tokens in a confidential balance, and issuers who want both extensions need additional freeze or approval settings. Do not invent a forensic claim from that sentence. Just do not assume clawback always reaches every balance type.

What a desk actually reads (ten minutes)

1. Name the mint. Not “SOL,” not “the wallet.” The token mint address.
2. Confirm the program. Explorer token pages show Token Program vs Token-2022. Wrong program id means you are reading the wrong account layout.
3. Freeze authority. Present, revoked (None), or a multisig. Glossary: freeze authority.
4. Extensions. If Token-2022, look for Permanent Delegate and Default Account State on the mint, not only on the user’s ATA.
5. Token account state. initialized / frozen. FreezeRadar surfaces this for registered USDC/USDT. For other mints, read the account on a Solana explorer.
6. If the mint is USDC or USDT in FreezeRadar’s registry, run scan on chain=solana with that asset. Do not paste an EVM blacklist getter.
7. If the mint is not registered, say so in the ticket. FreezeRadar will not invent a USDT-style DIRECT_ISSUER_BLACKLIST_MATCH for an unrelated RWA.

Venue holds still exist. A CEX that pauses SILV or USDC withdrawals is not the mint freeze. Split those tickets the same way you split exchange hold vs issuer USDT blacklist.

Worked example: freeze and clawback on the same mint (Dominion SILV)

This is uniqueness, not a second product landing. FreezeRadar does not register SILV. The point is the control plane.

Dominion’s public verify page states, in plain language, that SILV is not censorship resistant: Dominion holds freeze authority and a Token-2022 permanent delegate on the SILV mint; any SILV account can be frozen, and SILV can be transferred or burned from any account without the holder’s consent, under their Token Control Policy. Privileged actions are described there as multisig-governed with a timelock.

Bitquery’s public investigation of the 11 September 2026 exploit then shows those powers used in sequence: authority-multisig freeze waves on thousands of accounts, pool vaults included, then a later permanent-delegate test transfer of the smallest unit into treasury. That is freeze first, clawback capability second. It is not a USDC story and it is not a Tether addBlackList story.

Desk translation:

• If a user holds a Token-2022 RWA, read freeze authority and permanent delegate before you call the balance “theirs” in a liquidity or redemption sense.
• If freeze authority and permanent delegate sit on the same key, one compromise or one incident response can lock and move.
• Do not tell a USDC customer “this is what Circle will do to you.” Circle’s Solana USDC path is freeze-authority on a registered mint, documented through Circle’s terms and FreezeRadar’s Solana USDC landing.

Primary for the product claim is Dominion’s own verify page. Primary for the extensions is Solana’s Token-2022 documentation. Bitquery is a secondary timeline of one incident.

How this sits next to FreezeRadar scoring

AGENTS and methodology still win:

• Solana has no EVM/TRON-style issuer-blacklist registry for arbitrary mints.
• For registered USDC/USDT, a frozen token account is a direct freeze signal. Missing frozen is not a future-freeze forecast.
• Scoring still requires source-backed attribution. An explorer nickname is not a finding.
• Token-2022 permanent delegate on an unregistered mint does not become a FreezeRadar finding type. It is an ops reading you record in the ticket.

Do not rescore a historical Ethereum USDT scan using a Solana clawback anecdote.

Ticket language that keeps you honest

Good: “Solana USDC associated token account … is frozen on mint EPjF… (Circle USDC). FreezeRadar scan URL …. Venue withdrawal still untested.”

Good: “Token-2022 mint … shows freeze authority … and permanent delegate …. Not a FreezeRadar-registered asset. User should read issuer token-control policy. We did not run a USDT blacklist getter.”

Bad: “Wallet is blacklisted like USDT.” Solana freeze is account-state, not Tether’s isBlackListed mapping.

Bad: “Clawback incoming” on a classic SPL mint with freeze authority only.

Bad: “Unfreeze yourself by thawing.” Only the freeze authority can thaw. Desks do not publish thaw instructions as self-help against issuer controls.

Pre-transfer checklist for freezeable Solana USDC/USDT

1. Confirm chain is Solana and the address is canonical base58 (wallets service normalisation still applies: Solana is case-sensitive).
2. Confirm the mint is the registered Circle or Tether mint, not a wrapped lookalike.
3. Scan with chain=solana and the matching asset.
4. If the token account is already frozen, do not treat a later send as pending. It will not move.
5. Keep the signature, slot, and scan URL. Solana disputes are signature-first.

For Token-2022 RWAs your treasury actually holds, add two explorer reads: freeze authority and permanent delegate. Put both in the deal pack. That is still not a FreezeRadar score.

Honest limits

FreezeRadar does not enumerate every Token-2022 mint. It does not monitor Dominion, tokenized-stock mints, or permanent-delegate queues. Solana provider coverage is a bounded transfer window; truncated history lowers confidence and does not manufacture freeze risk. Official freeze docs can differ from older tutorials that claimed frozen accounts could still receive — prefer solana.com freeze-account over a blog memory.

This page does not help anyone evade a freeze, a clawback, or a lawful order. If your policy is “we do not hold assets with a permanent delegate,” write that in the SOP. Do not ask a scan product to hide the extension.

Related FreezeRadar surfaces

• Solana USDC freeze check
• Glossary: freeze authority · issuer-controlled assets
• USDT vs USDC desk view
• Technical freeze building blocks: how token freezing works in smart contracts
• Scan · Methodology

Key takeaway

On Solana, freeze locks a token account; Token-2022’s permanent delegate can move or burn without the holder. Read the mint’s program, freeze authority, and extensions before you reuse USDT blacklist language. Keep the USDC query on the existing Solana USDC landing. Treat SILV-style RWAs as a control-plane example, not a new FreezeRadar asset.