How to add custom RPC to Phantom? (Network settings)

Phantom Network Configuration Overview

1. Phantom wallet supports seamless integration with multiple EVM-compatible and Solana-based networks through its built-in network management interface.

2. Users can switch between default networks like Ethereum Mainnet, Polygon, BSC, and Solana without external configuration.

3. Custom RPC addition is required when connecting to testnets, Layer 2 rollups, or emerging chains not preloaded in the wallet.

4. The process differs slightly between desktop browser extension and mobile app versions due to UI constraints and permission models.

5. All custom network entries are stored locally on the device and never synced across devices unless manually backed up via seed phrase recovery.

Step-by-Step Custom RPC Entry

1. Open Phantom extension or mobile app and navigate to Settings → Networks → Add Network.

2. Select “Custom RPC” option instead of choosing from the preset list.

3. Input the exact chain ID as published by the blockchain’s official documentation — mismatched chain IDs will prevent transaction signing.

4. Paste the full HTTPS RPC endpoint URL; avoid HTTP or unsecured endpoints as Phantom blocks them by default.

5. Enter the native currency symbol (e.g., “ETH”, “MATIC”, “SOL”) — this controls how balances display in the asset list.

Verification and Validation Checks

1. After saving, Phantom attempts an immediate connection handshake using a lightweight JSON-RPC call (eth_chainId or solana_getVersion).

2. If the response returns valid metadata, the network appears as active in the dropdown menu with a green indicator.

3. A failed handshake triggers an error banner stating “Unable to connect to RPC node” — common causes include CORS misconfiguration or rate limiting.

4. Phantom does not cache invalid RPC responses; repeated failed attempts require manual re-entry of credentials.

5. No on-chain transaction is executed during verification — only metadata queries are issued.

Privacy and Infrastructure Considerations

1. Phantom routes all RPC requests through its own privacy proxy layer, stripping IP addresses before forwarding to upstream providers.

2. Third-party RPC partners such as QuickNode, Alchemy, and Helius do not receive identifiable user information from Phantom clients.

3. Users retain full control over which RPC endpoint they configure — Phantom neither enforces nor recommends specific providers.

4. Custom RPC configurations are isolated per network profile; switching networks does not carry over RPC settings.

5. Phantom explicitly states it cannot map IP addresses to wallet addresses or associate RPC usage patterns with individual users.

Frequently Asked Questions

Q: Can I add multiple custom RPC endpoints for the same chain ID?Phantom allows only one active RPC endpoint per chain ID. Duplicate entries overwrite previous configurations.

Q: Does Phantom support WebSocket (wss://) RPC URLs?Yes — Phantom accepts both HTTPS and WSS endpoints. WSS is preferred for real-time event subscriptions like pending transaction monitoring.

Q: Why does my custom network show “0x0” as balance even after successful connection?This occurs when the RPC node fails to return accurate account state — verify the endpoint serves eth_getBalance or getAccountInfo calls correctly.

Q: Is there a limit to how many custom networks I can store in Phantom?No hard limit exists, but excessive entries may slow down network switching latency due to sequential health checks during initialization.