How to Add a Second Wallet Account in Phantom

Understanding Phantom's Multi-Account Architecture

1. Phantom supports multiple accounts within a single wallet instance, each with its own unique public address and private key derivation path.

2. All accounts share the same Secret Recovery Phrase but are generated using BIP-44 hierarchical deterministic (HD) derivation with distinct account indices.

3. Account switching occurs locally in the browser extension or mobile app without network calls or external coordination.

4. Each account maintains independent transaction history, token balances, and NFT ownership records on-chain.

5. The primary account is created during initial setup; additional accounts are derived as child accounts under the same HD wallet root.

Step-by-Step Process for Adding a Second Account

1. Open the Phantom extension or mobile app and unlock it using your PIN, biometric authentication, or password.

2. Navigate to the top-right corner of the extension popup or the bottom navigation bar in the mobile app and tap the account avatar or name.

3. Select Add Account from the dropdown or modal menu — this option appears only when at least one account already exists.

4. Enter a custom label such as “Trading”, “Savings”, or “DAO Voting” to distinguish the new account’s purpose.

5. Confirm creation; Phantom instantly generates a new Solana-compatible address using the next sequential BIP-44 account index.

Security Implications of Multi-Account Usage

1. No additional backup is required — the second account is fully recoverable using the original 12-word Secret Recovery Phrase.

2. Phantom does not store account labels or metadata on remote servers; all naming data resides exclusively in local storage.

3. Signing requests are scoped per account: approving a transaction from Account A never grants access to Account B’s private keys.

4. Malicious dApps cannot enumerate or infer the existence of other accounts through standard Wallet Standard or EIP-1193 interfaces.

5. Exporting individual private keys is disabled by design — Phantom enforces full reliance on the recovery phrase for all account restoration.

Managing Token Visibility Across Accounts

1. Token auto-detection runs independently for each account, scanning associated token programs on Solana mainnet-beta or devnet.

2. Users may manually hide tokens in one account without affecting visibility settings in another account.

3. Custom RPC endpoints configured per network apply uniformly across all accounts — no per-account RPC override is supported.

4. NFT collections are fetched separately for each account using their respective wallet addresses, ensuring accurate display of owned assets.

5. Phantom’s balance aggregation layer displays total SOL and token values across all visible accounts unless explicitly filtered in the UI.

Frequently Asked Questions

Q: Can I import an externally generated Solana keypair as a second account in Phantom?A: No. Phantom only supports HD-derived accounts from its internal BIP-44 structure. External keypairs must be imported via the Secret Recovery Phrase of a compatible HD wallet.

Q: Does adding a second account increase gas fees or affect transaction priority?A: No. Transaction fees and priority fees are determined solely by network conditions and user-specified parameters, not by account count or derivation path.

Q: Are account labels synced across devices when restoring with the recovery phrase?A: No. Labels are stored locally and do not persist across device restores. Users must reassign labels after recovery on a new device.

Q: Can I delete a secondary account without affecting others?A: Yes. Deleting an account removes only its local address reference and label; all other accounts remain intact and fully functional.