A user receives ERC-20 tokens to their Bybit Wallet address but nothing appears in the token list. The wallet shows the correct network, the blockchain explorer confirms the transfer arrived, and the private key management is working as expected. Yet the token does not display in the interface, and no obvious button exists to add it. This is a common friction point in cryptocurrency wallet design: auto-import of tokens can be convenient, but it has real limits, and understanding when and why those limits apply is essential to effective token management.
Bybit Wallet’s multi-chain support across Ethereum, BNB Chain, Polygon, Arbitrum, and Optimism means users can receive tokens on multiple networks simultaneously. The wallet does automatically recognize and display ERC-20 and EVM-based tokens in most cases, but that automation is not universal. Some tokens fail to import, some networks have different token detection logic, and some legitimate assets are deliberately excluded for regulatory or security reasons. Rather than treating token visibility as either automatic or broken, users need to understand the decision tree: what the wallet is designed to detect, why some tokens require manual addition, and how to safely add custom token contracts without exposing the wallet to phishing or fraud.
Why Bybit Wallet auto-import works and where it stops
Bybit Wallet’s automatic token detection is built on ERC-20 standard recognition and on-chain indexing. When a token transfer lands in your wallet address, the wallet queries the blockchain to determine whether the contract implements the ERC-20 interface. If it does, the wallet retrieves the token name, symbol, and decimal places from the contract itself, then adds it to the display. This process happens in the background on supported networks, which is why most legitimate tokens appear without manual intervention.
The auto-import system has several practical constraints. First, the wallet must have indexed the contract already or must be able to fetch the contract data quickly. Second, the token contract must be deployed on a blockchain wallet network that Bybit supports—Ethereum mainnet, BNB Chain, Polygon, Arbitrum, and Optimism are the primary examples. Tokens on other networks such as Avalanche, Fantom, or Solana cannot be detected because Bybit Wallet does not maintain indexing or node connections for those chains. Third, the contract must follow the ERC-20 or EVM-equivalent token standard; non-standard or deliberately obfuscated contracts may fail to auto-detect.
Network congestion and indexing delays can also prevent immediate visibility. A large number of new token deployments might cause the wallet’s indexing service to lag, meaning a freshly created or recently bridged token may take hours to appear. If a token was deployed very recently or is extremely new, auto-import may be unavailable because the wallet has not yet cached the contract metadata. Additionally, tokens that failed security audits or that are flagged as high-risk may be intentionally excluded from auto-import even if they technically meet the ERC-20 standard. This is a safety feature, not a bug: the wallet developer chooses to prevent users from accidentally holding tokens associated with known scams or contract vulnerabilities.
Recognizing legitimate tokens versus manually adding contracts
Before manually adding any custom contract address, verify three pieces of information. First, confirm the contract address itself. Do not copy-paste from an email, chat message, or unverified website. Instead, go directly to the official project website or the project’s verified social media account and find the contract address there. Navigate to the blockchain explorer—Etherscan for Ethereum, BscScan for BNB Chain, Polygonscan for Polygon—and search the contract address. The explorer will show you the contract creation date, number of holders, transaction volume, and source code if it was verified.
Second, check whether the contract is verified and whether the source code matches the project’s claims. A verified contract on Etherscan, Polygonscan, or the equivalent chain-specific explorer shows the actual Solidity code, which you can read or have a security-conscious friend review. An unverified contract is a major red flag; it does not mean the contract is malicious, but it means you cannot see what it actually does. Third, confirm the token name and symbol match what you expect. Scammers frequently create near-identical copies of popular tokens—”USDT” versus “USDT_OLD,” “WETH” versus “wETH”—hoping users will add them to their wallets by mistake.
Once you have verified the contract address and symbol, the token management process in Bybit Wallet is straightforward: switch to the correct network, find the option to add a custom token, and enter the contract address. The wallet will fetch the token details and display a confirmation screen showing the name, symbol, and decimal places. At this point, compare these details to the official source one more time before confirming. Only after you have triple-checked should you approve the token for addition to your wallet.
How to manually add ERC-20 and EVM tokens to Bybit Wallet
The specific steps depend on whether you are using the Chrome extension or the mobile app, but the logic is identical. In the mobile version, open the app, navigate to the token or assets section, and look for an “Add Token” or “Custom Token” button. In the extension, the same button typically appears in the main assets view. Selecting it will open a form with fields for contract address, network selection, and sometimes optional fields for token name and decimal places.
Paste the verified contract address into the contract address field. The wallet will query the blockchain and auto-populate the token name, symbol, and decimal places if the contract is deployed and verified. Review these details carefully. If they match the official token details, confirm the addition. If they do not match or if the wallet fails to retrieve the information, stop and re-verify the contract address. A mismatch usually indicates a wrong address, a typo, or a fake contract.
After confirming, the token should appear in your wallet balance immediately, even if you have zero balance. It will display zero until a transfer arrives. This is the expected behavior. If you receive a transfer and the token still does not appear after a few minutes, the issue may be that you are on the wrong network. Bybit Wallet keeps tokens organized by network, so a token on Polygon will not appear in your Ethereum network view. Switch networks in the wallet interface and check whether the token appears there instead.
For NFT token management alongside fungible tokens, the same verification process applies if you are adding a custom NFT collection. Contract address, network, and verification status matter just as much for ERC-721 and ERC-1155 standards. However, NFT galleries in Bybit Wallet typically auto-detect more aggressively than fungible tokens do, so manual addition is less often necessary. If an NFT collection does not appear, verify the contract is deployed on a supported network and check the wallet’s settings for any collection visibility filters.
Security implications of custom token addition
Adding a custom token contract does not grant the contract any permission over your funds unless you explicitly approve it in a transaction. The wallet display alone is harmless—it simply shows a balance based on the contract’s public data. The security risk arises when you later interact with that token. If you attempt a token swap, provide liquidity, or transfer the token, your wallet will ask you to approve the contract as a token spender. That approval is when a malicious contract can extract value.
Approval mechanisms in EVM-based contracts follow a standard pattern: a user signs a transaction that allows a specific contract to transfer up to a specified amount of tokens on behalf of the user. A legitimate decentralized exchange, for example, needs this approval to execute a swap. A malicious contract can request an unlimited approval and then steal all tokens of that type held in the wallet. The approval itself is separate from and more powerful than the token display, which is why some users choose to grant limited approvals—for example, approving only the exact amount needed for one swap rather than unlimited approval.
The sites.google.com/mywalletcryptous.com/bybit-wallet resource documents the wallet’s built-in safeguards, which include transaction previews and warnings before you sign any contract interaction. Always read the preview carefully. If you are approving a token for a swap but the preview shows a very different action, cancel immediately. Use the blockchain explorer to double-check the contract address of the service you are interacting with, because phishing attacks often redirect users to a fake site with a subtly different URL or contract address.
Why some networks require different token management approaches
Not all supported networks handle token detection identically. Ethereum mainnet, the most established network, has extensive indexing infrastructure and therefore the most reliable auto-import. BNB Chain, Polygon, Arbitrum, and Optimism each have slightly different indexing capabilities and network conditions. The Ethereum Foundation maintains the core protocol and ERC-20 standard definition, but individual layer-2 and sidechain networks implement their own indexing services.
Polygon and Optimism are both EVM-compatible networks that follow the ERC-20 standard but may have different speeds for token detection depending on their respective network load and indexing service capacity. Arbitrum is similarly EVM-compatible but operates under its own sequencer and validation rules. The practical implication is that a token may auto-import immediately on Ethereum but take several minutes on a less-indexed layer-2 network. If you add a token to Polygon and it appears, then bridge the same token to Ethereum, the wallet should recognize it on Ethereum as well because the contract addresses will be different but both will conform to the ERC-20 standard.
Cross-chain token management therefore requires attention to contract addresses. When you bridge a token from Ethereum to Polygon, the destination address is a different contract, even though it represents the same underlying asset. Bybit Wallet’s bridging feature handles this mapping, but manually verifying the contract on the destination chain is still a good practice. A bridge from a reputable service such as Stargate or native bridges operated by the layer-2 network itself will produce a legitimate destination contract, but manually verifying the address on the block explorer before adding it to your token management list is an extra layer of protection.
Troubleshooting tokens that still do not appear
If a token transfer has landed in your wallet but the token does not appear after several minutes, work through these diagnostics in order. First, confirm you are viewing the correct network. Open the network selector in your wallet and verify that you are looking at the network where the token was sent. A common mistake is checking your Ethereum view when the token actually arrived on Polygon or Arbitrum. Check the blockchain explorer using your wallet address to see which network the transaction landed on, then switch your wallet to that network.
Second, verify the token contract address on the block explorer. Search your wallet address in the explorer, find the token transfer transaction, and click through to the token contract. Copy the exact contract address from the explorer. Then, in your wallet, use the “Add Token” feature and paste this address. If the wallet can retrieve the contract metadata, it will display the correct token name and symbol. If it cannot retrieve the metadata, the contract address is either wrong, the contract is not deployed on that network, or there is a temporary indexing issue.
Third, check the wallet’s token visibility settings. Some wallets allow users to hide or unhide tokens. If the token has been manually hidden in your wallet settings, it will not appear even though the balance exists on-chain. Look in the wallet’s preferences or settings menu for an option to manage visible tokens or token visibility. Fourth, confirm that the token contract is not on a network that Bybit Wallet does not support. Bybit Wallet supports Ethereum, BNB Chain, Polygon, Arbitrum, and Optimism, but not other EVM-compatible chains such as Avalanche, Fantom, or Harmony. If the token is on an unsupported network, the wallet cannot display it.
If all these steps pass and the token still does not appear, the contract may be deliberately excluded from auto-import for security reasons. In that case, manually adding the contract via the custom token feature should work if the contract address is correct. If manual addition also fails, wait a few hours and try again; temporary indexing delays can occasionally prevent token detection. If the problem persists, contact Bybit’s support with the contract address, transaction hash, and network, and they can investigate whether there is a known issue with that particular contract.
Best practices for ongoing token management and security
Effective token management is not a one-time setup; it is a continuous practice. Regularly audit your token list to remove tokens you no longer hold or use. Tokens that have zero balance still occupy space in your interface and can clutter your view. If you remove a token from your wallet view, the balance remains on the blockchain; you are only hiding the display. You can always add it back later if needed.
Keep your recovery phrase and backup secure, because compromising that backup compromises all token management and access to all your assets across all networks. Bybit Wallet supports both custodial cloud-based key management and non-custodial seed phrase options. If you choose cloud-based key management, your private keys are encrypted and stored on Bybit’s servers; this is more convenient for recovery but introduces custody risk. If you choose the seed phrase option, you remain fully responsible for the backup’s security. Either way, never photograph or share your recovery phrase, and never enter it on any website or in any app other than your own wallet during wallet setup or recovery.
For high-value token holdings, consider hardware wallet compatibility. Bybit Wallet integrates with Ledger and Trezor hardware wallets, allowing you to sign transactions on the hardware device itself rather than on your phone or computer. This significantly reduces the risk of malware or phishing compromising your private keys. The workflow is slightly slower because you must physically confirm transactions on the hardware device, but the security trade-off is worth it for significant balances.
Finally, treat token management as part of a larger security model. Biometric authentication (Face ID, Touch ID, fingerprint) on the wallet adds a layer of protection against casual access, but it does not protect a compromised device or a stolen recovery phrase. Two-factor authentication, if available for additional services you connect through the wallet, provides another checkpoint. The principle is layered security: no single mechanism is perfect, but multiple overlapping controls make compromise much harder.
Frequently asked questions
Why doesn’t my ERC-20 token show up in Bybit Wallet even though the blockchain explorer confirms I received it?
Auto-import may fail if the token was deployed very recently, the wallet has not yet indexed the contract, the token is on an unsupported network (Bybit Wallet supports Ethereum, BNB Chain, Polygon, Arbitrum, and Optimism), or the token is deliberately excluded for security reasons. Verify you are viewing the correct network in your wallet, then manually add the token using the verified contract address from the blockchain explorer.
How do I safely manually add a custom token to my cryptocurrency wallet without risking a scam?
Verify the contract address by visiting the official project website, then search the address on the blockchain explorer (Etherscan, Polygonscan, etc.) to confirm it is verified and matches the official token name. Never copy contract addresses from emails or unverified sources. Once you confirm the contract details in the explorer, use Bybit Wallet’s custom token addition feature to add it, review the wallet’s confirmation screen, and only approve if all details match.
Does adding a custom token contract to my wallet grant it permission to move my funds?
No. Displaying a token in your wallet does not grant any permissions. The security risk arises only when you approve the contract as a spender for transactions such as swaps or liquidity provision. At that point, a malicious contract could steal tokens if granted unlimited approval. Always review transaction previews before signing, and consider approving limited amounts rather than unlimited approval when possible.
Why is token management different across Ethereum, Polygon, and Optimism in Bybit Wallet?
All three networks follow the ERC-20 standard and are EVM-compatible, but they have different indexing services, network speeds, and infrastructure maturity. Ethereum has the most established indexing, so tokens usually appear immediately. Polygon and Optimism may experience longer delays during network congestion. Token management and manual addition work the same way on all networks, but auto-import timing can vary.