How to Revoke Token Permissions in Phantom After Using a Solana dApp?

Understanding Phantom Token Permissions

1. Phantom wallet maintains a granular permission model for Solana dApps, where each connected application receives explicit authorization to interact with specific tokens in the user’s wallet.

2. These permissions are stored locally on the device and are not broadcasted to the Solana blockchain, meaning revocation is purely a client-side operation.

3. Token permissions do not equate to private key exposure; Phantom never shares signing keys with dApps—only approved token accounts and program interactions are permitted.

4. A dApp may request access to SPL tokens such as USDC, BONK, or RAY, and Phantom displays these requests in clear language before approval.

5. Revoking permissions does not affect on-chain balances or historical transactions; it only prevents future programmatic transfers or approvals initiated by that dApp.

Navigating the Phantom Interface for Revocation

1. Open the Phantom browser extension or mobile app and ensure you are logged into the correct wallet.

2. Tap or click the three-dot menu icon located in the top-right corner of the wallet interface.

3. Select Connected Sites from the dropdown or sidebar navigation.

4. Locate the dApp entry corresponding to the Solana application you wish to revoke—entries display domain names like jupiter.exchange or raydium.io.

5. Click the trash can icon or “Remove Access” button next to the site name to initiate revocation.

Token-Level Permission Granularity

1. Phantom does not currently expose per-token toggle controls within the Connected Sites view—revocation applies to all token permissions granted to that dApp during connection.

2. If a dApp was granted access to both SOL and mSOL, removing the site removes access to both simultaneously.

3. Users cannot selectively retain access to one token while revoking another for the same dApp without reconnection and selective re-approval.

4. The wallet does not store token-specific allowance values (e.g., max spend limits), unlike Ethereum-based ERC-20 approvals—Solana’s model relies on account-level authority delegation.

5. No on-chain transaction is generated during revocation; the change exists solely in Phantom’s local storage layer.

Post-Revocation Behavior and Verification

1. After removal, the dApp will no longer appear in the Connected Sites list, and its UI will prompt for reconnection upon next visit.

2. Attempting to execute a token transfer or program instruction through the dApp will trigger Phantom’s standard connection dialog instead of auto-signing.

3. Users can verify revocation success by inspecting the dApp’s window.solana object in browser DevTools—the isConnected property returns false after removal.

4. Phantom does not send analytics or telemetry regarding revoked connections unless explicitly enabled by the user in privacy settings.

5. Local cache files containing permission metadata are overwritten immediately; no residual token identifiers remain accessible to the dApp’s JavaScript context.

Frequently Asked Questions

Q: Does revoking a dApp in Phantom also disconnect it from my Solana address book or saved contacts?A: No. Address book entries and contact labels are stored separately and persist independently of dApp connection status.

Q: Can a dApp regain access without my explicit re-approval after I revoke it?A: No. Phantom enforces strict opt-in reconnection. Any subsequent interaction requires manual confirmation via the wallet popup.

Q: Will revoking a dApp invalidate active staking positions or open limit orders?A: No. Staking contracts and order books reside on-chain and operate autonomously. Phantom’s revocation affects only future wallet-initiated actions.

Q: Is there a way to export or audit a full history of granted and revoked token permissions?A: Phantom does not provide an exportable audit log. Permission history is not retained beyond current active connections.