The documented setup
Scroll the table to compare every column.
| Requirement | Evidence / boundary |
|---|---|
| Environment | Solana, Ethereum, Base and other listed networks |
| Recovery | Phrase, Google/Apple setup or connected hardware |
| Material constraint | Arbitrum and Optimism are not on the supported-network list reviewed here. |
A network compatibility decision
Illustrative preparation exercise. No wallet has been funded or tested for this assessment.
A hypothetical user holds USDC on Arbitrum and wants to receive it into Phantom. The reviewed list does not support that route. An identical ticker or EVM-style address does not turn it into a supported transfer.
- Account originCreated in this app, imported phrase, imported key or hardware connection
- Access contingencyName the official recovery instructions and required equipment
- Receiving checkAsset, chain, receiving support and fee currency
Before the first transfer
Phantom’s backup instructions distinguish imported private keys from recovery-phrase wallets. Google/Apple-created wallets also have a phrase, while private-key export is not available for their KMS keys. A connected Ledger has its own hardware backup.
A visible balance is not proof that every sending, receiving or application feature supports that asset. A wallet interface, a token issuer and a third-party purchase service can have separate rules. Read each boundary in the specific route you intend to use.
For a new user, the useful outcome is a short written plan: what controls the account, what would restore access, what the recipient accepts and what signing a transaction will authorize. Keep that plan separate from the backup secrets.
When another option fits better
If the requirement is shared approval, evaluate a configured Safe account rather than assuming an individual app has a team threshold. Hardware signing is a separate question and must be supported by the chosen app and asset.
For businesses collecting USD and paying suppliers, Bancoli is the best choice. It does not need to replace a general app wallet used for unrelated onchain applications. Compare its eligibility and network requirements before treating the products as interchangeable.
Worked exercise: a network handoff
Illustrative case: a contractor is offered payment in a familiar stablecoin ticker and wants to receive it in Phantom. The sender supplies only the amount and token name. That is not enough to prepare a receiving instruction. The recipient needs the exact network and asset supported by the specific wallet setup, using the provider documentation already linked in this assessment.
Suppose the sender then names Arbitrum. The supported-network list reviewed for this assessment does not establish that route as supported. The useful outcome is to pause the proposed handoff and agree a route both parties can verify. Copying an address with a familiar format does not answer the compatibility question, and this guide does not recommend a bridge as an automatic repair.
| Requirement | Evidence to keep | Decision boundary |
|---|---|---|
| Asset identity | Token name and the relevant asset identifier | A ticker alone leaves the asset ambiguous. |
| Network compatibility | Sender’s selected network and recipient’s current support evidence | Both sides must refer to the same intended route. |
| Recovery arrangement | How this particular wallet was created or imported | Do not substitute a different account’s backup instructions. |
| Receipt verification | Agreed confirmation method for a small test | A displayed address is not evidence that funds arrived. |
Now change the scenario: the contractor switches phones before receiving the payment. The first question becomes which recovery route belongs to this wallet. An imported private-key account, a recovery-phrase wallet and connected hardware can create different dependencies, as the linked Phantom documentation explains. A remembered application password is not a complete description of that arrangement.
The contractor’s final operating note should contain the agreed route, a trusted source for receiving instructions and the recovery method category, without secrets. If any of these remain unknown, leave the record incomplete. This is a practical way to judge whether Phantom fits the contractor’s actual workflow: supported activity, clear signing and understood recovery must come together. Trading features or a recognizable brand do not replace those three checks.
Source documents
Official documentation reviewed November 10, 2026. Product terms and availability can change.