Trezor Wallet supports EVM networks through either Trezor Suite or MetaMask — Trezor Suite adds native networks directly using the [+] account selector, no RPC configuration needed.
MetaMask enables any unsupported Ethereum-based chain through custom RPC URL entry using EIP-3085. Trezor signs all transactions on the hardware device regardless of which interface initiates them.
| Path | When to Use | RPC Required | Browser Extension |
|---|---|---|---|
| Trezor Suite [+] | Natively supported chains | No | No |
| MetaMask + Trezor | Any unlisted EVM chain | Yes | Yes |
Understanding the three-layer architecture explains why some chains need MetaMask while others appear directly in Trezor Suite. Trezor firmware supports every EVM-compatible chain — the hardware device signs any valid EVM transaction regardless of the network. Trezor Suite displays a curated subset connecting through Trezor’s own verified node infrastructure, not user-specified endpoints.
| Layer | Function | User Action |
|---|---|---|
| Trezor firmware | Signs transactions, isolates keys on Secure Element | Physical button confirmation |
| Trezor Suite | Displays and manages natively supported networks | [+] to add supported chains |
| MetaMask | Configures custom EVM chains via JSON-RPC | Add custom network + Chainlist.org |
No. Trezor Suite does not accept custom RPC URL input. Network access is provided through Trezor’s own verified node infrastructure — this eliminates the malicious RPC endpoint attack vector present in software wallets. A malicious RPC endpoint can intercept JSON-RPC requests, read transaction data, and in some implementations substitute transaction destinations.
| Network | Type | Gas Token | Model Support |
|---|---|---|---|
| Bitcoin | L1 non-EVM | BTC | All |
| Ethereum | L1 EVM | ETH | All |
| Litecoin / Dogecoin / Bitcoin Cash | L1 | Native | All |
| XRP / Cardano / Solana | L1 | Native | Safe 3/5/7, Model T |
| Polygon PoS | L2 Sidechain | POL | All |
| BNB Smart Chain | L1 EVM | BNB | All |
| Arbitrum One / Base / Optimism | L2 Rollup | ETH | All |
All EVM-compatible networks share the same 0x address as the Ethereum account — adding Arbitrum does not create a new address. Arbitrum, Base, and Optimism are Optimistic Rollups that use ETH as gas — the OP and ARB tokens are ERC-20 governance tokens that cannot pay gas fees.
Trezor firmware supports all Ethereum-based chains — the limitation is in Trezor Suite’s curated interface, not the hardware. Chains like zkSync Era, Linea, Scroll, and Celo are EVM-compatible but not yet listed in Trezor Suite — they require MetaMask as the network configuration layer.
| Situation | Best Choice | Reason |
|---|---|---|
| Arbitrum, Base, Optimism, Polygon, BNB | Trezor Suite [+] | Natively listed — no RPC needed |
| zkSync Era, Linea, Scroll, Celo | MetaMask + Trezor | Not in native list |
| DeFi on listed chains | Trezor Suite WalletConnect | Direct dApp connection |
| Testnet access | MetaMask + Trezor | Testnets require custom RPC |
Install MetaMask, connect Trezor via USB and unlock with PIN.
MetaMask → account selector → Add account or hardware wallet → Trezor, then approve the public key export on device.
MetaMask → network selector → Add a custom network, entering Network Name, RPC URL, Chain ID, Currency Symbol, and Explorer URL.
Click Save and switch to the new network — all transactions route to Trezor for physical confirmation.
Chainlist.org aggregates verified RPC endpoints and Chain IDs for hundreds of EVM networks, triggering MetaMask’s EIP-3085 wallet_addEthereumChain standard for one-click registration. Community-verified endpoints are safer than manually searching unknown configurations.
Never add RPC endpoints received via Discord, Telegram, or social media — malicious JSON-RPC servers can intercept transaction data.
EVM address identity means all Ethereum-based chains derive wallet addresses from the same private key using identical algorithms — producing the same 0x address on every EVM network from a single Trezor seed. Ethereum and Avalanche C-Chain, for example, show the same 0x address even though they are completely separate blockchains with separate balances. This is the root cause of wrong network errors.
| Scenario | What Happens | Recovery |
|---|---|---|
| ETH sent on Arbitrum → Ethereum account selected | Invisible in ETH account | Add Arbitrum [+] in Trezor Suite |
| USDC sent on Polygon → Ethereum account | Invisible in ETH account | Add Polygon [+] in Trezor Suite |
| Tokens sent on unlisted chain | Invisible in Trezor Suite | MetaMask + add custom network |
| BTC sent to ETH address format | Rejected before broadcast | Transaction fails cleanly |
Assets sent to a Trezor address on an unsupported chain are not lost — they exist on the destination chain and can be recovered by connecting the device to MetaMask and adding the correct custom network.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Balance zero after adding Arbitrum | ETH is on a different chain | Verify which chain held the ETH |
| ERC-20 token not visible | Not auto-detected in Suite | Import token contract address |
| Balance visible in MetaMask, not Suite | Custom chain not in Suite | Use MetaMask view for that chain |
| Network sync delay | Temporary sync lag | Reload account, wait 30-60 seconds |
| Mistake | Result | Prevention |
|---|---|---|
| Expecting custom RPC in Trezor Suite | Feature not found | Use [+] for native chains; MetaMask for custom EVM |
| Using MetaMask for chains natively in Suite | Unnecessary complexity | Check [+] list first |
| Wrong Chain ID in MetaMask | Transaction failures | Verify on Chainlist.org before saving |
| Assuming same address = same balance | Empty balance confusion | Each network account shows separate balance |
| Using unverified RPC URL | JSON-RPC interception risk | Source endpoints from Chainlist.org only |
For natively supported chains: Trezor Suite → [+] → select network → Add Account. For unlisted chains: connect Trezor to MetaMask → Add a custom network with RPC URL and Chain ID from Chainlist.org.
Yes. Arbitrum One is natively supported — Trezor Suite → [+] → Arbitrum → Add Account. It shares the Ethereum 0x address with a separate balance, and ETH pays gas fees.
Yes, through MetaMask. Trezor firmware signs transactions on any EVM chain — connect via Trezor Connect and add the custom network using Chainlist.org for verified RPC endpoints and Chain IDs.
Trezor Suite → [+] → select Base or Polygon PoS → Add Account. Both are natively supported with no RPC entry required. Base uses ETH for gas; Polygon uses POL.
Natively in 2026: Bitcoin, Ethereum, Litecoin, Dogecoin, Ethereum Classic, Bitcoin Cash, XRP, Cardano, Solana, Polygon PoS, BNB Smart Chain, Arbitrum One, Base, and Optimism. All other EVM chains require MetaMask + Trezor Connect.
