How to enable "Auto-confirm" in Phantom? (DEX Trading)

Understanding Auto-confirm Functionality

1. Phantom Wallet introduced the Auto-confirm feature to streamline transaction signing during decentralized exchange interactions.

2. This setting bypasses manual confirmation prompts for known, low-risk contract calls such as standard token swaps on supported DEXs.

3. Auto-confirm only applies to pre-approved protocols and does not extend to arbitrary smart contract interactions or wallet transfers.

4. The feature relies on internal signature whitelisting maintained by Phantom’s security team, updated with each major wallet release.

5. Users retain full control over which DEXs are included in the auto-approval list via the wallet’s permission management interface.

Accessing Auto-confirm Settings

1. Launch the Phantom browser extension or mobile app and unlock your wallet using your password or biometric authentication.

2. Navigate to the gear icon in the top-right corner to open Settings, then select “Security & Privacy” from the left-hand menu.

3. Scroll down to locate the “Auto-confirm transactions” toggle switch beneath the “Transaction Preferences” section.

4. Click the toggle to enable it—Phantom will display a warning dialog outlining scope limitations before final activation.

5. After enabling, the wallet displays a small badge next to supported DEX names in the swap interface indicating auto-confirmation readiness.

Supported DEXs and Contract Validation

1. As of current wallet version 3.12.0, Auto-confirm is active for Raydium, Orca, Jupiter, and Marginfi on Solana mainnet.

2. Each DEX must pass Phantom’s audit criteria including verified bytecode, immutable routing contracts, and absence of dynamic delegate calls.

3. Phantom cross-references deployed contract addresses against its internal registry before permitting auto-signing during swap initiation.

4. Users can view the full list of whitelisted contracts by expanding the “Approved Protocols” subsection within Security & Privacy settings.

5. Contracts flagged for re-audit due to upgrades or governance changes are temporarily excluded until verification completes.

Risks and Mitigation Measures

1. Enabling Auto-confirm reduces exposure to phishing-based signature traps but increases vulnerability to malicious contract upgrades on trusted platforms.

2. Phantom enforces strict bytecode immutability checks; any deviation triggers immediate deactivation of auto-signing for that contract instance.

3. Transaction simulation runs client-side before submission to detect unexpected state changes or token transfers outside the user’s intent.

4. Users receive real-time notifications for every auto-signed transaction, including gas estimates and execution timestamps.

5. A one-click “Revoke All Auto-permissions” button resides at the bottom of the Security & Privacy page for rapid response to suspicious activity.

Frequently Asked Questions

Q: Does Auto-confirm work with wrapped tokens like wSOL or renBTC?Yes. Phantom validates wrapped token contracts independently and includes them in the auto-approval list if they meet bytecode and deployment criteria.

Q: Can I enable Auto-confirm only for specific DEXs instead of all at once?No. The toggle operates globally. However, you may manually remove individual DEX permissions via the “Manage Approved Protocols” section after enabling the feature.

Q: Why does Auto-confirm deactivate when I switch networks?Phantom maintains separate whitelists per network. Auto-confirm must be re-enabled individually for devnet, testnet, and mainnet due to differing contract deployments and audit statuses.

Q: Is there a delay between DEX contract updates and Auto-confirm reactivation?Yes. Phantom typically requires 24–72 hours to complete bytecode verification and deploy updated signatures across wallet versions following a DEX upgrade.