How to use the Phantom "Refuel" feature? (Gas Coverage)

Understanding Phantom Refuel Mechanics

1. Phantom Refuel is a gas coverage service integrated directly into the Phantom wallet interface, designed to help users execute transactions on Solana without holding native SOL for fees.

2. The feature operates by partnering with third-party providers like Jito and Helius to supply temporary SOL to cover network transaction costs.

3. Users do not need to pre-approve or sign additional smart contracts beyond standard wallet permissions—activation occurs at the moment of transaction submission.

4. Coverage is limited to single-use per transaction and does not extend to program deployments, cross-chain swaps, or complex multi-instruction operations unless explicitly supported by the provider’s current configuration.

5. Refuel amounts are dynamically calculated based on real-time Solana network fee estimates and may vary depending on instruction complexity and cluster load.

Eligibility and Wallet Requirements

1. Only Phantom wallets connected to the mainnet-beta Solana network can access Refuel—devnet and testnet configurations disable the option entirely.

2. The wallet must be unlocked and have an active session; hardware wallet integrations (e.g., Ledger) do not support Refuel due to signature constraints.

3. Accounts must possess a valid token balance in at least one SPL token supported by the underlying refuel provider—commonly USDC, SOL, or mSOL.

4. Phantom enforces a minimum token balance threshold before enabling the toggle: 0.01 USDC or equivalent value in another supported asset.

5. Users flagged for repeated failed transactions or abnormal behavior may experience temporary suspension from using the feature without notification.

Step-by-Step Activation Flow

1. Initiate any Solana-based action requiring gas—such as NFT minting, token swap, or wallet-to-wallet transfer—through a dApp that supports Phantom’s wallet adapter.

2. When the Phantom confirmation modal appears, locate the “Enable Refuel” toggle in the bottom-left corner beneath the fee summary.

3. Flip the toggle to activate; Phantom will immediately query available providers and display the estimated covered amount alongside the original fee.

4. Confirm the transaction using your standard wallet password or biometric prompt—the signed message includes embedded metadata indicating refuel usage.

5. Upon successful broadcast, the transaction hash appears in the activity feed, and a small “Refueled” badge renders next to the entry in the history tab.

Provider-Specific Limitations

1. Jito-powered refuels restrict coverage to transactions under 200,000 compute units; exceeding this triggers automatic fallback to standard SOL payment.

2. Helius-backed requests require inclusion in a specific priority fee tier—transactions submitted outside designated time windows may fail silently.

3. No refunds are issued if a refueled transaction reverts due to logical errors in the instruction set or insufficient account tokens.

4. Providers rotate dynamically per region and time zone; users in APAC may receive different backend routing than those in EMEA or AMER clusters.

5. Refuel does not apply to staking instructions or validator-related operations—even when initiated via Phantom’s built-in staking UI.

Frequently Asked Questions

Q: Does Refuel work with Phantom’s mobile app?A: Yes, but only on iOS version 2.12.0+ and Android version 2.13.1+. Earlier builds omit the toggle entirely.

Q: Can I use Refuel to pay for multiple pending transactions simultaneously?A: No. Each transaction requires individual activation—there is no batch refuel mode or queue-based coverage system.

Q: Is the refueled SOL deducted from my wallet balance later?A: No. The SOL used is supplied by the provider and not debited from any user-held asset. There is no repayment obligation.

Q: Why does the Refuel toggle disappear during certain NFT mints?A: Some mint programs enforce strict instruction validation that conflicts with provider metadata injection—Phantom hides the toggle preemptively to avoid failed submissions.