How to Add a Network to Trust Wallet (Custom RPC Guide)
Learn to connect any blockchain network to Trust Wallet safely
Preparing Accurate Network Details Before You Start
Before you add a custom network to Trust Wallet, you need to gather four critical pieces of information to avoid costly mistakes that could lead to lost funds or failed transactions. These include the RPC URL, Chain ID, native token symbol, and block explorer URL. RPC, or Remote Procedure Call, acts as a bridge between your Trust Wallet and the blockchain you want to connect to—without a reliable, official RPC URL, your wallet can’t sync with the network or process actions. It’s non-negotiable to source these details from official channels, not random third-party websites, as scammers often create fake RPC links designed to steal private keys or drain funds. For example, if you plan to add Cronos Mainnet (a popular EVM-compatible blockchain), you’d get its official RPC URL from Cronos Labs’ developer documentation: https://evm.cronos.org. Its Chain ID is 25, native token symbol is CRO, and block explorer is https://cronoscan.com. You must also confirm you’re using the right details for the network’s version—mainnet vs. testnet—since mixing Chain IDs is one of the most common user errors. For instance, Binance Smart Chain (BSC) mainnet uses Chain ID 56, while its testnet uses 97; entering the wrong one would make you interact with an entirely different blockchain than intended.
Step-by-Step Process to Add a Custom Network
Once you have all verified details, adding the network is straightforward, even for new Trust Wallet users. Let’s walk through the process using the example of adding BSC Testnet (ideal for testing decentralized apps without real crypto) to your wallet. First, open the Trust Wallet app on your iOS or Android device—there’s no difference in steps between the two operating systems. Next, tap the gear-shaped settings icon in the top right corner of the main wallet screen to access your settings menu. Scroll down until you see the “Networks” option under the Wallet section, then tap it. You’ll see a list of pre-configured networks Trust Wallet supports by default, such as Ethereum, Polygon, and Solana. To add a custom network, locate the “Add Network” button at the bottom of this screen and tap it. You’ll now see a form where you need to input each detail you prepared earlier. For BSC Testnet, fill in the RPC URL as https://data-seed-prebsc-1-s1.binance.org:8545, Chain ID as 97, Symbol as tBNB, and Block Explorer as https://testnet.bscscan.com. Take your time to type every value correctly—even a small typo, like an extra character in the RPC URL, will prevent your wallet from connecting. Once all fields are complete, tap the “Save” button in the top right corner. After saving, BSC Testnet will appear in your network list. To switch to this network, return to the main wallet screen, tap the current network name at the top (usually Ethereum by default), then select BSC Testnet from the dropdown. If you’re using a testnet, you’ll need to get free test tokens from a public faucet (like BSC Testnet Faucet) to cover gas fees for transactions—this is a key step to ensure you can interact with DApps on the testnet.
Troubleshooting Common Issues After Adding a Custom Network
Even with careful preparation, you may encounter small hiccups when using a new custom network. The most frequent problem is a “connection failed” error when switching to the network, which almost always stems from an outdated or incorrect RPC URL. If this happens, first confirm the RPC URL with the network’s official docs—chain operators sometimes update their endpoints to improve stability, so using an old link can break connectivity. Another common issue is a Chain ID mismatch, which leads to seeing the wrong network’s balances. For example, if you intended to add Cronos Mainnet but entered the testnet Chain ID (338), your wallet will show testnet CRO instead of mainnet CRO. To fix this, go back to the Networks screen, find your custom network, tap the pencil-shaped edit icon next to it, correct the Chain ID, and save the changes. You might also notice missing tokens after adding the network—remember that adding the network alone doesn’t add its tokens; you’ll need to manually add each custom token using its unique contract address on that network, which is a separate but simple step. For transaction failures, check two key points: first, do you have enough of the native network token (like CRO for Cronos or tBNB for BSC Testnet) to cover gas fees? Low gas balance will cause transactions to get stuck. Second, note that some niche EVM chains have longer block times—wait 1-5 minutes for confirmations instead of expecting instant processing like Ethereum. Finally, avoid relying on DApps to auto-switch networks, as they can sometimes mislead you into connecting to fake networks; always double-check the network name in Trust Wallet before interacting with any DApp.
TAG:
