Skip to main content
Version: Current guides

Manage networks, RPC nodes and asset visibility

Networks, nodes and tokens are different​

The network determines which chain holds an asset. An RPC node is the connection the app uses to read and submit information on that chain. A token contract distinguishes tokens on the same network. Changing nodes does not bridge assets; adding a token does not create a balance or establish that it is trustworthy.

The management actions below apply only where your current version provides the relevant entry. Adding a network or token does not establish support for private payments, card top-ups or OTC. Check each service's payment screen separately.

Show, hide and add networks​

If your current version provides this entry, open Profile/Settings → Network management.

  1. Select a network and check its name and Chain ID. A mainnet and testnet with similar names are different networks.
  2. If visibility controls are available, enable the network you need, then select it on the asset screen. Hiding a network changes the visible list without deleting on-chain assets.
  3. To add a custom network, obtain its name, RPC URL, Chain ID, native currency symbol and explorer address from verified official network information. Complete the fields requested by the current form.
  4. Wait for connection and chain checks before saving. For a connection failure, check the URL and connectivity. For a chain mismatch, stop and verify the information rather than changing the Chain ID arbitrarily to bypass the error.
  5. After saving, select the network and check that balances and the explorer refer to the same chain before making payments.

Supported custom chain types depend on the current form. Entering a URL does not establish support for every non-EVM network. Check existing entries for duplicate chain IDs. Built-in networks may restrict editing; delete a custom network only where allowed. Removing its configuration does not move funds or cancel submitted transactions. Keep the network and transaction information needed for later checks.

Add, select and remove RPC nodes​

If your current version provides multiple nodes, open the network's node list:

  1. Check the selected node and full URL. Add a trusted node URL and, if offered, a recognizable label.
  2. Wait for reachability and chain checks before adding it. Opening a webpage does not establish that it is an RPC endpoint for the correct network.
  3. Select a node and refresh the asset screen. If the app reports an automatic switch, check the selected node before reviewing the data again.
  4. Keep at least one verified working node before removing unused entries. After removing the selected node, check which one is now active. If removing the last node is blocked, do not delete the whole network as a substitute.

Automatic switching addresses connection failures. It does not fix insufficient funds, failed transaction execution or incorrect recipients. If all nodes are unavailable, restore connectivity or choose a trusted working node instead of sending again. A node may observe queries and your network source. Do not expose a private node URL containing access credentials in public screenshots or support messages.

Token contracts and custom imports​

If your current version provides Add token/Custom token:

  1. Select the correct network and obtain the full contract address for that network from verified official token-project information.
  2. Enter the address and check the detected name, symbol, decimals and other displayed fields. Matching names or icons do not establish the same asset. Do not rely solely on search results or addresses sent by strangers.
  3. If recognition fails or metadata disagrees, verify the network and contract first. Do not guess decimals to make a balance look correct.
  4. After confirming, return to the original account and network and refresh. Adding a token affects recognition or display; it does not move a same-named token from another network.

If the entry is missing or the contract is unsupported, retain the transaction hash and contract information and ask official support about display support. Do not connect to an unfamiliar airdrop website, approve tokens or provide recovery material merely to display it.

Check display settings before assuming funds are missing​

SituationCheck
Numbers are replaced by asterisksUse the eye control if available; hiding amounts does not hide blockchain records
Small token balances are absentDisable Hide small balances if available; the threshold depends on the current screen
Empty list after switching networksCheck the account, network and visibility controls; switching does not bridge funds
Token quantity exists but fiat estimate is missingCheck price-data availability; no estimate does not mean no tokens
Persistent loading or an old balanceCheck the node and refresh; cached balances are not proof of currently spendable funds

If receipt remains unclear after payment, check the original transaction using Transaction records and Missing transfers. Repeatedly adding a token or paying again will not resolve it.