![\"Solflare](\"https:\/\/lh3.googleusercontent.com\/sitesv\/AG8ngQWT4buxGnzuVj_Z8d6DViLi2tuKj1boYn-6qmqrwM0PVG3pboGfZmk2ZaQ_k2Wv_qSAhDhlZOaEaoipvU7y6-gGFdcYd7ARVFDcXtF52NGVhJMc0WiRqi4QYj7iUs5c3wtjgRlh85gOLIMWn0RW3UwFucCSGyyALIJNM8R_Iunry40vxsxKBrfoykUMYJUiUijbNln0stsnt2Qt6frH\")
<\/p>\nA new Solana user installs Solflare, deposits SOL, and sees their balance. Then they receive a transfer of a less common SPL token\u2014a token built on the Solana blockchain\u2014and find nothing arrives in their wallet despite the transaction confirming on-chain. The token was sent to the correct address. The blockchain shows the transfer completed. Yet the wallet displays no activity, no balance, and no indication the token exists. This is not a loss; the funds remain on the blockchain under that wallet’s control. But understanding why they do not appear, and how to make them visible, separates a frustrating experience from a functional one.<\/p>\n
The root cause is straightforward but often invisible to users accustomed to other blockchain wallets: Solflare, like most Solana wallets, does not automatically recognize every SPL token. The wallet maintains a curated list of well-known tokens for convenience and security, but thousands of SPL tokens exist. Smaller projects, newer tokens, or specialized contracts simply do not appear unless the user explicitly adds them. The process is not difficult, but it requires understanding how Solana token accounts work and knowing where to find the contract address that makes a token identifiable on-chain.<\/p>\n
Ethereum and similar blockchains store token balances in a single contract that tracks ownership across addresses. Solana uses a different model: each token account is its own on-chain object. When someone sends you a USDC token on Solana, they are not updating a ledger; they are transferring a discrete account that holds that token type. That account is linked to your wallet and marked as owned by you, but it only exists if it was created. Many wallets, including Solflare, will automatically create the necessary token account when you first receive a token, but only if they recognize the token’s contract address and decide to display it in the interface.<\/p>\n
The contract address<\/strong> is a unique identifier that defines what a token is. Every SPL token has one. USDC on Solana, for example, has a specific contract address that is different from USDC on Ethereum or any other blockchain. When you receive a token, the transfer references this contract address. Solflare needs to know this address to recognize the token, fetch its symbol and decimal places, and display your balance. If Solflare has never heard of the contract, it will not show the token by default, even though the token account exists on-chain and belongs to your wallet.<\/p>\n This design has security implications. A wallet that automatically displays every token transferred to it could be exploited by spam or scams. An attacker could create a worthless token with a name similar to something valuable and send it to thousands of addresses, creating confusion or clicking mistakes. By requiring explicit addition of tokens, Solflare puts the user in control and reduces the risk of accidental interaction with a malicious contract. The trade-off is that legitimate, smaller tokens will not appear until the user takes action.<\/p>\n The good news is that the token account and the funds are always there on the blockchain. Adding the token to your wallet is a display operation; it does not move money or create new accounts. You are simply telling Solflare to recognize and show something that already exists under your control. The process requires only the contract address and takes seconds.<\/p>\n Before you can add a token to Solflare, you need its contract address. This is not something the wallet generates; it is a permanent identifier published on the Solana blockchain when the token was created. Several reliable sources provide this information. The most straightforward is Solscan, the leading Solana blockchain explorer. Visit solscan.io, search for the token’s name or symbol, and navigate to its token page. The contract address appears prominently near the top, usually labeled as “Token Address” or “Mint.” You can copy this address directly from the explorer.<\/p>\n Another source is the official project website or documentation. If you received the token from a specific project, they should publish the contract address clearly to help users add it to their wallets. Projects aware of the Solana ecosystem understand this friction point and make the address easy to find. If the address is not published anywhere on the official site, that is a red flag worth investigating before trusting or interacting further with the project.<\/p>\n CoinGecko and other token aggregators also list SPL token contract addresses. These services index tokens from multiple chains, so you need to verify you are looking at the Solana version of the token. Ethereum has USDC. Polygon has USDC. Solana has USDC with its own contract address. Mixing them up would result in you adding the wrong token or being unable to find the one you own.<\/p>\n One practical precaution: verify the address against multiple sources before entering it into your wallet. A common scam involves publishing a fake contract address that looks almost identical to the real one. If you copy the address from Solscan, the official project site, and a second explorer and all three match, you are extremely unlikely to be adding a malicious contract. Once you have confirmed the address, copy it precisely\u2014even one character wrong will not work and will not add the token.<\/p>\n Open the Solflare extension in your browser. You should see your wallet’s SOL balance and a list of tokens already displayed. Near the bottom or in a menu, you will find an option to add a new token; this may be labeled “Add Token,” “Import Token,” or similar depending on your version. Click it. You will see a field asking for a contract address or mint address. This is where you paste the contract address you found. Solflare will immediately fetch information about the token from the Solana blockchain: its name, symbol, decimal places, and current price if available. Review this information to ensure it matches what you expect. If the token name is unfamiliar or the symbol does not match what you were told to expect, do not proceed; it may not be the correct contract.<\/p>\n Once you confirm the token details are correct, approve the addition. Solflare will add it to your token list, and your balance should appear immediately if you have any of that token. If the balance shows zero, either the token account has not been created yet or the transfer did not complete. Check the transaction history on Solscan using your wallet address to verify the transfer went through. If the transfer is confirmed on-chain but does not show in Solflare, wait a moment and refresh the extension; sometimes there is a brief synchronization delay.<\/p>\n The token should remain in your list after you add it. If you remove it from the display, you can add it again using the same process. Removing a token from Solflare does not affect the actual token account on-chain or your balance. It is only a display preference. Similarly, if you import your wallet into another Solana wallet\u2014such as by using your seed phrase\u2014you would need to add the custom token again in that new wallet application, as each wallet maintains its own display list.<\/p>\n If you have added the contract address but still see no balance, verify several things. First, confirm that the transfer actually completed. Go to Solscan and search for your wallet address. Look at the token transfers section and check if the transaction you expected appears there. If it shows “pending,” wait longer. If it shows “failed,” the transfer did not go through; contact whoever sent you the token. If it shows “confirmed” but the amount does not match what you expected, you may have received fewer tokens than anticipated, perhaps due to a transfer fee or wrong decimal handling.<\/p>\n Second, verify that you added the exact correct contract address. Solflare will not prevent you from adding a wrong address; it will simply add a token that is not what you intended. Go back to Solscan, search for the token by name, and compare the contract address shown there to the one in your wallet. If they do not match exactly, delete the incorrect token from Solflare and add the correct one.<\/p>\n Third, check if a token account actually exists. On Solana, receiving a token sometimes requires the recipient’s wallet to create a token account first. Some wallets do this automatically; Solflare typically does. But if something went wrong, the transfer might have failed because no account existed to receive it. You can verify this on Solscan by looking at your wallet address and checking under “Token Accounts.” You should see a listed account for each token type you own, identified by its contract address. If the token account does not exist, the transfer likely failed and the funds remain with the sender.<\/p>\nFinding the contract address for an SPL token<\/h2>\n
Adding a custom token to Solflare step by step<\/h2>\n
Troubleshooting when the token still will not appear<\/h2>\n