How to change the RPC node in Phantom? (Network Settings)

Accessing Network Configuration in Phantom

1. Open the Phantom browser extension or mobile application and ensure you are logged into your wallet.

2. Click or tap the network indicator—usually displayed as a small icon near the top-right corner of the interface, showing the current network name like “Ethereum Mainnet” or “Solana Mainnet Beta”.

3. A dropdown or modal menu appears listing available networks. Select “Custom RPC” or “Add Network” depending on your Phantom version.

4. Enter the required fields: Network Name, RPC URL, Chain ID (if applicable), Currency Symbol, and Block Explorer URL.

5. Save the configuration. Phantom validates the RPC endpoint before adding it to your network list.

Verifying RPC Endpoint Compatibility

1. Not all RPC URLs support the same features. Phantom requires endpoints that expose standard JSON-RPC methods such as eth_blockNumber, eth_getBalance, and eth_sendRawTransaction for Ethereum-compatible chains.

2. For Solana, the node must respond to getSlot, getBalance, and sendTransaction via HTTP or HTTPS.

3. Avoid using rate-limited or public free tiers with aggressive throttling—these may cause transaction failures or inconsistent balance updates.

4. Test the RPC URL independently using curl or a tool like Postman before entering it into Phantom.

5. Confirm TLS certificate validity if using HTTPS; self-signed or expired certificates will prevent Phantom from connecting.

Managing Multiple Custom Networks

1. Phantom allows users to store multiple custom RPC configurations simultaneously—each appearing as a selectable option in the network switcher.

2. To rename or delete a custom network, navigate to Settings → Networks → select the target entry → choose “Edit” or “Remove”.

3. Duplicate entries with identical RPC URLs but different names are permitted but may cause confusion during wallet interactions.

4. Switching between networks triggers an automatic reload of account balances and recent transactions associated with that chain.

5. Some dApps detect Phantom’s active network and auto-adjust their UI or contract interaction logic accordingly—this behavior relies entirely on accurate RPC metadata.

Troubleshooting Connection Failures

1. If Phantom displays “Failed to connect to network”, verify the RPC URL has no trailing slashes or typos—e.g., https://rpc.example.com/ should be https://rpc.example.com.

2. Check whether CORS headers are enabled on the RPC server; Phantom enforces strict cross-origin policies when calling external endpoints.

3. Disable browser extensions that interfere with network requests, such as ad blockers or privacy tools that strip headers or block third-party domains.

4. Ensure your local firewall or corporate proxy does not filter outbound HTTPS requests to non-standard ports.

5. Reboot the Phantom extension after saving changes—cached connection states sometimes persist despite updated settings.

Frequently Asked Questions

Q: Can I use a localhost RPC node with Phantom browser extension?A: Yes, provided your browser allows insecure localhost connections and the node runs over HTTPS or is served via a valid development certificate. HTTP localhost endpoints are blocked by Chromium-based browsers.

Q: Why does Phantom show zero balance after switching to a custom RPC?A: The node may not have fully synced, or it might serve stale data. Try refreshing the page or checking the node’s latest block height against a public explorer.

Q: Does Phantom support WebSocket RPC endpoints?A: No. Phantom exclusively uses HTTP/HTTPS-based JSON-RPC. WebSocket URLs (ws:// or wss://) are ignored during network setup.

Q: Can I export or import my custom RPC configurations across devices?A: Phantom does not offer native import/export for network settings. You must manually re-enter each custom RPC configuration on every device or browser profile.