Token Guard
Inspect the selected Token-2022 controls supported by the scanner and mark gaps explicitly.
Audit arbitrary transfer-hook logic or claim exhaustive coverage of every extension.
Optional extensions add behaviour beyond basic transfers. The enabled extensions matter more than the token’s marketing.
Extensions are optional and configuration-specific.
Mint-level and account-level features differ.
Extra authorities can remain after mint authority is removed.
Two tokens can look identical in a wallet while behaving differently during transfers. Understand the configured features before relying on a simple mint-authority check.
Walk through the flow. Each step gives you one practical question to investigate.
Token-2022 supports optional account and mint extensions. Many must be planned at initialization, and some combinations are incompatible.
Conceptual flow, not a live transaction trace. Use the sources below for implementation details.
Read the configured fee and the keys that can change settings or withdraw withheld amounts. Avoid assuming a displayed amount is the amount received.
Look for TransferFeeConfig + relevant token-account extensionsDetermine whether this privileged delegate is configured and how its key is controlled.
Look for PermanentDelegate extensionIdentify transfer-hook programs, default account state, pausing, and non-transferable behaviour where applicable. Unsupported decoding remains unknown.
Look for Enabled extension inventory + program-specific reviewPublic Token-2022 source and clients. The guide does not assert that any particular mint enables these features.
Resolving its default branch and pinning one commit.
Read-only · No account connection · No code executionInspect the selected Token-2022 controls supported by the scanner and mark gaps explicitly.
Audit arbitrary transfer-hook logic or claim exhaustive coverage of every extension.
Inspect a public implementation’s declared structure and supported source patterns.
Execute the program or establish runtime safety.
We’ll prefill the target. You review the scope before anything runs.
Live launches require verified holder access.Do retained authorities match the published token policy?
Is every enabled extension supported by the intended venue?
Has any external hook program received a separate review?
Which checks returned unknown, and what evidence would resolve them?