EVM Chain Token Lists in Rabby: Why Some Custom Tokens Disappear and How to Re-Import Them

A user opens Rabby Wallet on their Chrome browser, navigates to an Ethereum or Polygon network, and discovers that a custom token they added weeks ago is no longer visible in their portfolio. The token contract address still exists on the blockchain, transactions to and from the address are readable on the block explorer, and the balance is still there—but the wallet interface shows nothing. This situation occurs frequently enough that it warrants a clear explanation of how Rabby manages token lists, when and why tokens become hidden, and the exact steps required to restore visibility without losing access to the underlying assets.

The core issue is not a security failure or a permanent loss of funds. Rabby uses a combination of curated token lists, user-added custom tokens, and automatic network detection to populate the tokens displayed in your wallet interface. When a token disappears from view, it typically reflects a change in one of those sources—a list update, a network switch, a cache refresh, or a discrepancy between the wallet’s internal tracking and the blockchain’s actual state. Understanding the mechanics behind token visibility, recognizing the difference between a token being hidden and a token being lost, and knowing how to manually re-add tokens is essential for any user who interacts with lesser-known assets, yield farming tokens, or emerging blockchain projects.

How Rabby Manages Token Lists and Visibility

Rabby displays tokens through a hierarchy of sources. At the top level, the wallet includes curated token lists for major networks—Ethereum mainnet, Arbitrum, Optimism, Polygon, Base, and others—sourced from established providers such as Uniswap, 1inch, and community-maintained registries. These lists are updated periodically as tokens gain adoption or lose relevance. Below those are user-imported tokens, which the wallet stores locally on the device and associates with specific addresses and networks. Finally, there is the watch-only layer: if you import an address without the corresponding private key, the wallet scans that address’s holdings on the configured network and attempts to display them using available token information.

The critical detail is that curated lists are dynamic. When Rabby updates its token sources, a token that was previously included may be removed if it no longer meets inclusion criteria, if the list maintainers determine it is inactive or fraudulent, or if it is pruned to keep the list performant. This removal does not delete your holdings. It simply means the wallet will no longer automatically recognize transfers involving that token’s contract address when you first encounter them. Your balance remains on the blockchain; the wallet simply stops displaying it without explicit re-addition.

User-added custom tokens are more stable because they are stored locally within the wallet’s database on your device. However, custom tokens can still disappear under specific conditions: a browser extension update that clears local storage, an accidental removal from the wallet’s settings, a switch between different Rabby installations (such as moving from a desktop version to the Chrome extension), or a manual exclusion you may have forgotten about. The Rabby Chrome extension and mobile app maintain separate token lists, so a custom token added on iOS will not automatically appear in the Chrome version unless you re-add it there.

Why Tokens Vanish After Network Changes or Updates

One of the most common scenarios involves switching between EVM-compatible networks. Rabby’s automatic network selection feature detects which blockchain your wallet is interacting with based on recent transaction activity or the site you are visiting. When you switch from Ethereum to Polygon, the token list refreshes to show Polygon-specific tokens. If a token you added exists only on Ethereum, it will disappear from the display when you navigate to Polygon. This is not a bug; it is intentional design to reduce clutter and prevent confusion between tokens with identical names on different chains.

However, some users add the same token contract address under the wrong network, which creates a mismatch. For example, a token contract address that exists on Ethereum may not exist on Polygon with the same address. If you manually add the Ethereum address while viewing Polygon, the token will not appear on Polygon because the contract is not deployed there. When you return to Ethereum, the token should reappear, but if it does not, the issue may be that the token’s metadata—its name, symbol, or decimals—failed to load from the blockchain the first time, and the wallet cached an invalid entry.

Browser extension updates can also trigger token list recalculations. Rabby periodically releases updates that improve token detection, add new networks, or refine the underlying token list logic. During these updates, cached token data may be cleared, and the wallet must re-fetch information from the blockchain. If that process encounters network delays or errors, some tokens may fail to re-load and will appear missing until the data is manually refreshed or the wallet is restarted.

Distinguishing Between Hidden, Removed, and Lost Tokens

Before troubleshooting, it is important to clarify what has actually happened. A hidden token is one that exists in the wallet’s database or on the blockchain but is not currently displayed. A removed token is one that you deleted from your custom list or that was pruned from a curated list. A lost token would be one where the contract address no longer exists on the blockchain or where you have truly lost the private key to access funds. Each situation requires a different response.

To check whether a token is genuinely lost or merely hidden, navigate to a blockchain explorer such as Etherscan, Polygonscan, or the appropriate block explorer for your network. Enter your wallet address and search your transaction history. If you see transfers involving the token’s contract address, the token exists and your access is intact. The issue is visibility in Rabby, not the underlying asset. If the block explorer shows no balance and no recent transfers, the token may be legitimately gone—either the contract was abandoned, the balance was sent elsewhere, or the contract address you are checking is incorrect.

Another diagnostic step is to check Rabby’s internal token cache. In the wallet’s settings menu, you can typically view or manage your custom token list. Look for the token by its name or contract address. If it appears in the list but is grayed out or marked as inactive, the wallet has recognized it at some point but cannot currently display it due to metadata loading issues. If it does not appear in the list at all, you will need to re-add it manually.

Step-by-Step: Re-Adding a Custom Token to Rabby

Re-importing a token into Rabby requires only the contract address and, in some cases, the token’s symbol and decimal places. The most reliable source for this information is the contract address itself, as it is immutable on the blockchain. Open the token’s contract page on a block explorer—Etherscan for Ethereum, Polygonscan for Polygon, Arbiscan for Arbitrum, and so on. Copy the contract address (it will be a long hexadecimal string starting with “0x”). Make note of the token symbol and the number of decimals, which you can find in the contract’s “Read” section under the name, symbol, and decimals functions.

In Rabby, navigate to the token management section. This is typically found in the wallet settings or by clicking an “Add Token” button in your token portfolio view. Ensure you are on the correct network before adding the token. Select “Custom Token” and paste the contract address into the designated field. The wallet will attempt to fetch the token’s metadata automatically from the blockchain. If successful, the name, symbol, and decimals will populate themselves. Review these fields to ensure accuracy—incorrect decimals in particular can cause the wallet to display a balance that is magnified or reduced by orders of magnitude.

Once you have verified the token details, confirm the addition. The token should now appear in your portfolio view on the correct network. If it still does not appear after adding, try these troubleshooting steps: clear your browser cache if using the Chrome extension, disconnect and reconnect any hardware wallet you are using, restart the extension, or check whether Rabby is displaying a “loading” state while it synchronizes with the blockchain.

When Curated Lists Update and Remove Your Tokens

Rabby’s curated token lists are maintained by community contributors and third-party sources. These lists can and do change. A token that was included in Uniswap’s default list, for example, may be removed if it falls below trading volume thresholds, if its contract contains security vulnerabilities, or if it is flagged as potentially fraudulent. Users of an EVM wallet need to understand that relying on a curated list means accepting that list maintainers’ judgments will determine visibility, whether or not you agree with their assessment of a token’s legitimacy.

When a curated list removes a token, Rabby will stop displaying it unless you have explicitly added it as a custom token. If you frequently use tokens that are not on major lists—such as governance tokens from smaller DAOs, newly launched assets, or specialized yield farming tokens—the best practice is to proactively add them as custom tokens rather than relying on curated list inclusion. This gives you control over visibility independent of upstream list changes.

You can also configure which token lists Rabby uses in its settings. Some versions of the wallet allow you to enable or disable specific curated lists, or to add your own custom list sources. If you find that a particular list repeatedly removes tokens you care about, you can disable it and rely on custom additions instead. This trade-off is between convenience—curated lists reduce the number of tokens you must manage—and control, where custom tokens guarantee visibility unless you explicitly remove them.

Preventing Token Visibility Issues Going Forward

The most effective long-term strategy is to treat custom token addition as part of your normal workflow when you encounter a new token. Rather than waiting until you receive a transfer or deposit, add the token as a custom entry as soon as you identify a contract address you will be interacting with. This ensures that when transfers occur, the wallet will recognize them immediately and display the balance correctly. Document the contract addresses of tokens you use regularly in a secure note or password manager, separate from your recovery phrase. This allows you to quickly re-add tokens if you switch devices or reinstall the wallet.

Keep your Rabby extension or app updated. While updates can occasionally cause token list recalculations, they also include bug fixes and improvements to token detection. Delaying updates in hopes of preserving token visibility often has the opposite effect, as older versions may have stale cached data. Before updating, you can export your token list or take a screenshot of your portfolio as a backup reference, though this is rarely necessary for token recovery.

For tokens you hold in significant quantities, consider using a hardware wallet integrated with Rabby. Hardware wallets maintain their own token tracking independent of the software wallet interface, so even if Rabby’s display fails, your asset access through the hardware device remains unaffected. This adds a layer of redundancy and security. To set up a hardware wallet with Rabby, connect your device (such as a Ledger or Trezor), authorize Rabby to display your holdings, and then add custom tokens as needed. The connection should survive browser restarts and extension updates.

Using Block Explorers as a Fallback Verification Tool

At any point where you doubt whether Rabby is displaying accurate balances, you can verify the true state of your holdings using a blockchain explorer. Open Etherscan, Polygonscan, or the relevant explorer for your network, and enter your wallet address. The explorer will show every token transfer to and from your address, your current balance for each token, and the contract addresses involved. This serves as the source of truth when Rabby’s interface is unclear or when you suspect a display error.

Some explorers also display the token’s metadata, including its symbol, name, total supply, and holder count. If the explorer shows a balance but Rabby does not, the issue is definitely on Rabby’s side—likely a missing custom token entry or a corrupted cached entry. If the explorer shows no balance, the tokens have genuinely been transferred elsewhere or the contract address is incorrect. This distinction is critical: troubleshooting a display issue in Rabby is straightforward, while recovering tokens that have been moved or lost to the wrong address requires different steps.

For users downloading Rabby for the first time or reinstalling after a device change, verify that you are using the official source. The wallet is available through the Chrome Web Store, Edge Add-ons, Brave’s extension marketplace, and official app stores for iOS and Android. Some third-party distribution sites may host older or modified versions. If you have concerns about the authenticity of your installation, download directly from the official rabby.io domain and compare the extension ID or app version number with the information listed on the official site.

Recovering Tokens After an Accidental Removal

If you accidentally deleted a custom token from Rabby, recovery is simple: follow the re-addition steps described earlier. The token’s contract address and metadata do not change; you are simply re-registering it within Rabby’s interface. Your actual holdings on the blockchain are unaffected. The only scenario where recovery becomes complex is if you deleted the wallet itself without exporting the recovery phrase or if you lost access to the device where the wallet was installed. In those cases, importing the recovery phrase into a new Rabby installation or another wallet is necessary to regain control of the underlying assets.

For users with watch-only addresses (addresses you can view but cannot spend from), token visibility depends entirely on Rabby’s ability to recognize and display holdings at that address. Watch-only addresses cannot send tokens, approve smart contracts, or perform any transaction that would require a signature. They are purely for monitoring. If tokens disappear from a watch-only address view, use the same custom token re-addition process. The watch-only address will then display the token’s balance without requiring any private key or transaction signing.

Document your custom token additions in a separate file if you manage many tokens across multiple networks. Include the contract address, symbol, network, and decimal places. This becomes invaluable if you need to restore Rabby on a different device, switch to a different wallet, or troubleshoot token visibility issues. Keep this file encrypted and backed up securely, alongside your recovery phrase backup. The file is not sensitive to the same degree as a recovery phrase—it contains no private information, only token identification data—but it should still be protected from casual access or loss.