How to add custom RPC networks to Trust Wallet? (Advanced Settings)

Accessing Advanced Network Settings

1. Open the Trust Wallet application on your mobile device and ensure you are logged into your wallet.

2. Tap the wallet icon in the bottom navigation bar to view your asset dashboard.

3. Select the three-dot menu in the top-right corner and choose Settings from the dropdown list.

4. Scroll down and tap Preferences, then locate and select Networks.

5. Tap the + Add Network button at the bottom of the screen to initiate manual RPC configuration.

Entering Custom RPC Parameters

1. Input a recognizable Network Name, such as “Arbitrum One” or “Base Mainnet”, to distinguish it later.

2. Paste the full RPC URL—this must be a functional, HTTPS-enabled endpoint with no trailing slash (e.g., https://arb1.arbitrum.io/rpc).

3. Specify the Chain ID as a decimal integer matching the target network’s official identifier (e.g., 42161 for Arbitrum One).

4. Enter the Symbol for the native token (e.g., ETH, BNB, MATIC) used on that chain.

5. Provide the Block Explorer URL including the protocol prefix (e.g., https://arbiscan.io) — this enables transaction verification directly from Trust Wallet.

Verifying Chain Compatibility and Token Recognition

1. After saving the network, return to the wallet home screen and tap the network selector at the top.

2. Confirm the newly added network appears in the list and is selectable without error.

3. Navigate to the Receive section while on the custom network to verify address generation matches expected format (e.g., Ethereum-style checksum addresses).

4. Attempt to add a token contract manually using its verified address and correct decimals — successful balance display confirms proper EVM compatibility.

5. Check if transactions broadcasted through the custom RPC reflect on the associated block explorer within seconds, indicating node responsiveness and correct chain alignment.

Troubleshooting Common Configuration Failures

1. If the wallet displays “Invalid RPC” or fails to load balances, recheck the RPC URL for typos, missing “https://”, or unsupported authentication headers.

2. A “Wrong Chain ID” warning means the entered value does not match the network’s canonical identifier — consult official documentation or chainlist.org for verification.

3. Missing token balances after adding a contract may stem from incorrect decimal specification or an unverified proxy contract — always cross-reference with Etherscan or equivalent explorers.

4. Slow transaction confirmations or failed sends often indicate RPC endpoint overload or rate limiting — switch to an alternate provider like Alchemy, Infura, or a community-maintained public node.

5. Inability to switch networks inside DApp browsers may result from outdated Trust Wallet version — update via App Store or Google Play before retrying.

Frequently Asked Questions

Q: Can I add non-EVM chains like Solana or Cosmos to Trust Wallet using custom RPC?A: No. Trust Wallet’s custom network interface only supports EVM-compatible blockchains. Solana, Cosmos, and other non-EVM ecosystems require native integration and cannot be added via RPC settings.

Q: Why does my custom network disappear after updating Trust Wallet?A: Network configurations persist across updates unless manually deleted or corrupted during cache reset. If lost, re-enter parameters using the same steps — no backup export functionality exists for custom RPC entries.

Q: Is it safe to use third-party RPC endpoints?A: Public RPC providers vary in reliability and privacy practices. Avoid endpoints requesting API keys embedded in URLs or those hosted on suspicious domains. Prefer well-documented services with transparent uptime records.

Q: Can I rename or edit an existing custom network?A: Yes. Go to Settings → Preferences → Networks, tap the network name, then select the pencil icon to modify any field except Chain ID — changing the Chain ID will break compatibility and require recreation.