Trust Wallet adds a Custom Network by accepting five fields – Network Name, Symbol, RPC URL, Chain ID, and Block Explorer URL – through its mobile app or Browser Extension. Only EVM-compatible networks can be added manually.
| Field | Role | Required |
| Network Name | Human-readable label for the chain | ✅ Yes |
| Network Symbol | Native currency ticker (e.g. ETH, MATIC) | ✅ Yes |
| RPC URL | Node address Trust Wallet uses to communicate with the chain | ✅ Yes |
| Chain ID | Unique numeric identifier for the blockchain | ✅ Yes |
| Block Explorer URL | Link to on-chain transaction viewer | Optional |
A Custom Network is a blockchain not pre-configured in Trust Wallet. Adding one teaches the wallet how to communicate with that chain’s nodes – enabling token access, dApp interaction, and transaction signing.
Trust Wallet supports EVM-compatible Custom Networks because EVM chains share Ethereum’s transaction signing standard – the same private key and address format work across all of them. Non-EVM chains (Bitcoin, Solana, Cosmos) require separate architecture and are added only through official Trust Wallet integration.
| Network Type | Manual Addition | Example Chains |
| EVM-compatible | Yes – via RPC URL + Chain ID | Polygon, Avalanche, Base, Arbitrum, Fantom |
| Non-EVM | No – official integration only | Bitcoin, Solana, Cosmos, Tron |
Trust Wallet natively supports 100+ blockchains – including Ethereum, BNB Chain, Solana, Polygon, Avalanche, Arbitrum, Base, Optimism, and Tron – without any manual configuration. Newer, emerging, or less popular EVM chains require manual Custom Network addition.
| Support Type | Networks Included | User Action Required |
| Native (100+ chains) | ETH, BNB, SOL, MATIC, AVAX, ARB, BASE, OP, TRX | None – pre-configured |
| Manual Custom Network | New EVM chains, testnets, sidechains, lesser-known L2s | RPC URL + Chain ID entry |
Before adding a Custom Network, search Trust Wallet’s built-in network list. Most major chains are already natively supported – manual addition is only needed for emerging or niche EVM networks.
Five fields define a Custom Network in Trust Wallet. Each field serves a specific technical function — an error in any one field causes the network to malfunction or transactions to fail.
An RPC URL is the address of a blockchain node that Trust Wallet uses to read balances, broadcast transactions, and interact with smart contracts. A wrong or malicious RPC URL causes incorrect balance display or exposes transaction data to third parties.
| RPC URL Source | Trust Level | Use Case |
| Chainlist.org (green status) | High – community verified | Best for most users |
| Official project documentation | High – primary source | Most reliable |
| Infura / Alchemy / QuickNode | High – institutional providers | High-volume users |
| Unknown third-party sites | Low – unverified | Avoid entirely |
| Social media / Telegram links | Very Low – Malicious RPC risk | Never use |
Chain ID is a unique numeric identifier assigned to each EVM blockchain. Trust Wallet uses Chain ID to route transactions to the correct network. An incorrect Chain ID causes transactions to broadcast on the wrong chain — resulting in failed transactions or permanent fund loss.
| Chain | Chain ID | Native Currency |
| Ethereum Mainnet | 1 | ETH |
| BNB Smart Chain | 56 | BNB |
| Polygon Mainnet | 137 | MATIC/POL |
| Avalanche C-Chain | 43114 | AVAX |
| Arbitrum One | 42161 | ETH |
| Base | 8453 | ETH |
| Optimism | 10 | ETH |
| Fantom | 250 | FTM |
Chain ID must match the official network identifier to ensure correct transaction routing.
A wrong Chain ID sends transactions to unintended blockchains. Chain ID conflicts occur when duplicate IDs exist. Chainlist displays verified Chain IDs for all supported EVM networks.
Block Explorer URL is optional in Trust Wallet’s Custom Network form. Adding it enables in-app transaction tracking — tapping a transaction opens the chain’s explorer directly. Without it, users must manually visit the explorer to check transaction status.
| Block Explorer | Chain | URL |
| Etherscan | Ethereum | etherscan.io |
| BscScan | BNB Chain | bscscan.com |
| Polygonscan | Polygon | polygonscan.com |
| Snowtrace | Avalanche | snowtrace.io |
| Arbiscan | Arbitrum | arbiscan.io |
| Basescan | Base | basescan.org |
Trust Wallet mobile adds a Custom Network through the manage assets icon. The Network tab — separate from the Token tab — is where custom chain details are entered and saved.
Chainlist.org lists RPC URLs for 1,000+ EVM networks with live status indicators. A green status confirms the node is responding. Copy the green-status RPC URL before opening Trust Wallet.
Steps on Chainlist:
| Chainlist Status | Meaning | Action |
| 🟢 Green | Node live and responding | ✅ Safe to use |
| 🔴 Red | Node offline or slow | ❌ Do not use |
| ⚪ Grey | Status unknown | ❌ Avoid – use green only |
Steps – Trust Wallet Mobile App:
If the chain is not yet verified in Trust Wallet’s assets repository, the token price and icon will not display – the network still functions correctly for transactions.
Example — Adding Polygon Mainnet:
| Field | Value |
| Network Name | Polygon Mainnet |
| Network Symbol | MATIC |
| RPC URL | https://polygon-rpc.com |
| Chain ID | 137 |
| Block Explorer URL | https://polygonscan.com |
Example — Adding Avalanche C-Chain:
| Field | Value |
| Network Name | Avalanche C-Chain |
| Network Symbol | AVAX |
| RPC URL | https://api.avax.network/ext/bc/C/rpc |
| Chain ID | 43114 |
| Block Explorer URL | https://snowtrace.io |
The Trust Wallet Browser Extension adds Custom Networks through the Settings menu — a different path from the mobile app. The extension is available on Chrome, Brave, Edge, and Opera.
Mobile app uses the manage assets icon and Network tab. The Browser Extension uses Settings → Network → Add Custom Network. Both require identical fields — the path to reach the form differs.
| Step | Mobile App | Browser Extension |
| Open form | Manage assets icon → ‘+’ → Network tab | Settings icon → Network → Add Custom Network |
| Fields required | Name, Symbol, RPC URL, Chain ID, Explorer | Name, Symbol, RPC URL, Chain ID, Explorer |
| Save action | Tap Save | Tap Add / Save |
| Available on | iOS and Android | Chrome, Brave, Edge, Opera |
Steps — Trust Wallet Browser Extension:
The Browser Extension and mobile app share wallet access when the same recovery phrase is imported – but Custom Networks added on one platform must be re-added on the other manually.
Adding a Custom Network is safe when the RPC URL comes from a verified source. A Malicious RPC cannot steal funds or access private keys — but it can read transaction data and display false balances.
A Malicious RPC monitors transaction requests sent through it. It sees destination addresses, amounts, and token types before they reach the blockchain. It cannot initiate transactions, move funds, or access the recovery phrase.
| Malicious RPC Capability | Can Do | Cannot Do |
| Read transaction data | Yes | — |
| Display false balance | Yes | — |
| Front-run transactions | Yes – on some networks | — |
| Access private keys | — | No |
| Sign transactions | — | No |
| Move funds without approval | — | No |
| Access recovery phrase | — | No |
Verify RPC URLs using three sources in priority order: official project documentation first, Chainlist green-status confirmation second, institutional providers (Infura, Alchemy, QuickNode) third. Never use URLs shared via Telegram, Discord DMs, or unknown websites.
| Verification Step | Action | Risk Level if Skipped |
| Check official project docs | Search “[network name] official RPC” | High |
| Confirm green status on Chainlist | Visit chainlist.org → search network | Medium |
| Cross-reference Chain ID | Verify Chain ID matches official docs | High |
| Test with small transaction | Send minimal amount first | Medium |
Chainlist green status confirms a node is live but does not guarantee benign ownership.
Cross-referencing the Chain ID eliminates the risk of connecting to the wrong chain via a correct-looking URL. A test transaction validates correct network function before larger transfers.
A Custom Network fails to appear or function in Trust Wallet due to four common causes: incorrect RPC URL, wrong Chain ID, offline RPC node, or app version mismatch.
| Cause | Symptom | Fix |
| Incorrect RPC URL | Network added but transactions fail | Re-enter URL from Chainlist green-status node |
| Wrong Chain ID | Transactions route to wrong network | Verify Chain ID on Chainlist or official docs |
| RPC node offline | Network added but balance won’t load | Switch to alternate green-status RPC URL |
| Outdated Trust Wallet version | Form fields not saving correctly | Update Trust Wallet to latest version |
| Non-EVM network attempted | Network tab unavailable or form rejects | Only EVM-compatible chains can be added manually |
No price or icon means the chain is not yet verified in Trust Wallet’s official assets repository. The Custom Network still functions — transactions, token display, and dApp interaction all work. Only price data and branding are absent until Trust Wallet verifies the chain.
| Display Status | Meaning | Impact on Functionality |
| No icon shown | Chain unverified in Trust Wallet repo | Cosmetic only – no functional impact |
| No price data | Token not in Trust Wallet price feed | Cosmetic only – balance still visible |
| Network listed | Chain added successfully | Full transaction capability |
| Network missing | Save failed — check fields | Re-enter all fields and retry |
Open Trust Wallet, tap the manage assets icon, tap ‘+’, switch to the Network tab, enter the Network Name, Symbol, RPC URL, Chain ID, and optional Block Explorer URL, then tap Save. Use Chainlist.org to find verified RPC URLs with green status.
Find verified RPC URLs on Chainlist.org — search the network name and copy a green-status URL. Also check the official project documentation under “Connect Wallet” or “Network Configuration.” Never use RPC URLs from Telegram, Discord DMs, or unknown websites.
Chain ID is a unique numeric identifier for each EVM blockchain. Trust Wallet uses it to route transactions to the correct network. Common Chain IDs: Ethereum = 1, BNB Chain = 56, Polygon = 137, Avalanche = 43114, Base = 8453. A wrong Chain ID causes transactions to fail or route to the wrong chain.
No. Trust Wallet only supports EVM-compatible Custom Networks for manual addition. Non-EVM chains like Bitcoin, Solana, Cosmos, and Tron are supported through official Trust Wallet native integration — not manual RPC entry. Check Trust Wallet’s native network list before attempting manual addition.
A Custom Network fails to appear due to an incorrect RPC URL, wrong Chain ID, offline RPC node, or outdated Trust Wallet version. Re-enter all fields using a green-status RPC URL from Chainlist and the verified Chain ID from official project documentation. Update the app if fields are not saving.
Adding Custom Networks is safe when using verified RPC URLs from Chainlist or official project documentation. A Malicious RPC cannot access private keys or move funds — it can only read transaction data. Never use RPC URLs shared via Telegram or unknown websites.
Chainlist.org is a community-verified directory of EVM network RPC URLs and Chain IDs. It is widely used and cross-referenced with official project documentation. Always confirm green RPC status on Chainlist and cross-check the Chain ID against official docs before adding any Custom Network.
Click the Trust Wallet extension icon, unlock the wallet, click Settings (bottom right), click Network, then click Add Custom Network. Enter Network Name, Symbol, RPC URL, Chain ID, and optional Block Explorer URL. Click Save, then select the new network from the dropdown to activate it.
