How to Add a Custom Token to a Crypto Wallet

Adding a custom token to a crypto wallet means manually adding a token contract so the wallet can display a token balance that may not appear automatically. This does not create new tokens, recover lost funds, or move assets. It only helps the wallet interface recognize and show a token that may already exist at a wallet address on a specific blockchain network. Before adding any custom token, users should understand the difference between a public address and secret wallet information. For the basics, read What Is a Crypto Wallet Address? and Wallet Address vs Private Key.

This topic matters because token display is one of the most common beginner wallet problems. A user may receive a token, open a wallet, and think the token is missing because the wallet does not show it. In many cases, the token may exist on-chain, but the wallet interface has not imported the token contract yet. In other cases, the user may be on the wrong network, checking the wrong wallet address, using a fake token contract, trusting a copied ticker, or viewing a wallet interface that has not indexed the token. For network-specific context, read What Is a Blockchain Network? and Why Wallet Network Matters.

This guide explains how to add a custom token safely in plain English. It covers what a custom token is, why some tokens do not appear automatically, how to verify the token contract, how to check the correct network, what token decimals mean, how to use a block explorer, what mistakes to avoid, and when not to import a token at all. This page is neutral education. It is not a recommendation to use any specific wallet, exchange, token, protocol, bridge, claim page, or wallet-connected service.

Quick answer

Adding a custom token means entering a token contract address into a wallet so the wallet can display that token on the correct network. It matters because wallet apps do not always show every token automatically, especially new, small, custom, bridged, or manually issued tokens. Before adding a custom token, users should verify the official token contract, confirm the selected network, check the wallet address on a block explorer, and never enter a private key or seed phrase into any token import page.

Why this matters

Wallets are one of the most important parts of crypto because they are where users view addresses, balances, networks, transactions, tokens, signatures, and permissions. A wallet can make blockchain activity easier to use, but it can also hide important technical details behind short labels and quick buttons. Users should understand what the wallet is showing before they send, sign, approve, import, claim, bridge, swap, or connect.

Custom token import matters because a wallet balance screen is not the same as the blockchain itself. A token may exist on-chain even when the wallet interface does not show it. A wallet may also show a token symbol that looks familiar even when the contract is fake. This is why the token contract address and network matter more than the token name, ticker, logo, or random message from someone online.

The main safety rule is simple: public information and secret information are different. A wallet address can usually be shared to receive funds or check a block explorer. A token contract can usually be checked publicly. A private key, seed phrase, recovery phrase, or secret phrase should never be entered into a website, support form, direct message, random token tool, fake wallet repair page, or custom token import page. If a page asks for secret wallet information, review How to Avoid Crypto Scams before continuing.

The basic idea

A crypto wallet is best understood as an interface for managing keys, addresses, networks, balances, transactions, and wallet requests. The wallet does not usually “store” coins like a physical container. Instead, it helps the user view and authorize activity related to blockchain records. When a token does not appear, the issue may be with wallet display, network selection, token contract recognition, token indexing, or the actual on-chain balance.

1. A custom token is added by contract address

A custom token is usually imported by entering the token contract address into a wallet. The contract address identifies the token on a specific blockchain network. The wallet may then detect the token symbol and decimals automatically, or the user may need to enter them manually. The most important part is the contract address, not the name or logo.

2. A token contract belongs to one network

Token contracts are network-specific. A token contract on Ethereum is not the same as a token contract on BNB Smart Chain, Base, Arbitrum, Polygon, Solana, Tron, or another network. Some assets may have versions on multiple chains, but each network has its own address format, explorer, contract, and token record. This is why the selected network must match the token contract.

3. Adding a token does not move funds

Importing a token into a wallet display does not send, receive, approve, bridge, swap, claim, or recover funds. It only changes what the wallet interface shows. If a token is not actually at the wallet address on that network, adding the contract will not create a balance.

4. Wallet balances are network-specific

A wallet can show different balances on different networks. The same wallet interface may display Ethereum, BNB Smart Chain, Base, Arbitrum, Polygon, Solana, Tron, or another network separately. If a balance does not appear, the first checks are usually the selected network, wallet address, token contract, and block explorer. For more detail, see Why Wallet Balance Does Not Show.

5. Token names and symbols can be copied

A token symbol is not proof that a token is real. Anyone can create a token with a familiar name or ticker on many networks. A fake token can copy the name, logo, and symbol of a known asset. The safer way to identify a token is to verify the contract address from an official source and compare it with the correct network explorer.

6. Wallet requests are not all the same

Adding a token for display is different from signing a message, approving token spending, connecting to a dApp, or sending a transaction. A normal custom token import should not require the user to reveal a seed phrase or approve a token spender. If the process suddenly asks for a signature, approval, private key, or recovery phrase, stop and verify the source.

What users need before adding a custom token

Before importing a token, users should gather the correct information. The exact wallet interface may vary, but most custom token imports require the same basic details: network, token contract address, token symbol, and token decimals. In many modern wallets, symbol and decimals may fill automatically after the contract is entered.

• Correct network: The blockchain where the token exists, such as Ethereum, BNB Smart Chain, Base, Arbitrum, Polygon, Solana, Tron, or another network.
• Token contract address: The official contract address for the token on that exact network.
• Token symbol: The short ticker shown by the wallet, such as a few letters. This should not be trusted alone.
• Token decimals: The number used by the token contract to display human-readable balances.
• Wallet address: The public wallet address where the token should appear.
• Block explorer: The correct explorer for the network, used to confirm the token transfer or balance.
• Official source: The project website, documentation, verified explorer page, or trusted announcement source for the contract.

Step-by-step: how to add a custom token

The exact buttons may differ between wallet apps, but the safe process is similar across most wallets. The goal is not to click quickly. The goal is to verify that the wallet is on the correct network and that the token contract is the real contract for the token the user expects.

Step 1: Confirm the wallet address

First, confirm that the wallet address is the address that should hold the token. If the token was sent to a different address, importing the token into the current wallet will not show a balance. Copy the wallet address from the wallet and compare it with the address used in the transfer, exchange withdrawal, bridge, presale, claim, airdrop, or payment.

If the user is checking a transaction, the transaction hash can be opened on the correct block explorer. The explorer should show the sender, recipient, token transfer event, token contract, network, timestamp, and status. If the transfer went to a different wallet address, a custom token import cannot fix that.

Step 2: Select the correct network

Next, switch the wallet to the network where the token exists. This is one of the most common mistakes. A token sent on BNB Smart Chain will not appear under Ethereum. A token sent on Base will not appear under Arbitrum. A token sent on Polygon will not appear under BNB Smart Chain. The wallet must be viewing the correct chain.

Network names can also be confusing because the same asset may exist on many networks. For example, a stablecoin may have versions on Ethereum, BNB Smart Chain, Base, Arbitrum, Polygon, Solana, Tron, and other chains. The token symbol may look similar, but the contract and network are different. For deeper context, read Why Wallet Network Matters.

Step 3: Find the official token contract

The token contract should come from an official or trusted source. Safer sources may include the project's official website, official documentation, a verified block explorer page, a trusted token list, or an official announcement channel. Avoid copying contract addresses from random comments, direct messages, fake support accounts, paid search ads, copied social media profiles, or unknown claim pages.

When checking a contract, compare the network, contract address, token name, symbol, decimals, verified source, and explorer history. If the project says the token is on one network but the contract you found is on another, stop and verify. If there are many tokens with the same symbol, do not guess.

Step 4: Open the custom token import screen

In most wallet interfaces, the user can find an option such as “Import token,” “Add token,” “Custom token,” “Manage tokens,” or “Add asset.” The label may vary, but the purpose is the same: telling the wallet interface to watch and display a token contract on the selected network.

This step should not require a seed phrase, private key, recovery phrase, secret phrase, or support verification. A wallet may ask the user to confirm adding a token to the interface, but it should not require private wallet access material. If it does, stop.

Step 5: Paste the token contract address

Paste the verified token contract address into the custom token field. If the wallet supports automatic detection, it may fill the token symbol and token decimals automatically. Users should still compare the detected information with the official source or block explorer. Automatic detection is helpful, but it does not replace verification.

If the wallet says the contract is invalid, the selected network may be wrong, the address may be from a different chain, the contract may not follow the expected token standard, or the address may have been copied incorrectly. Do not force a token import from an unknown source just because the symbol looks familiar.

Step 6: Check token symbol and decimals

Token decimals control how the wallet displays the raw token amount as a human-readable balance. Many tokens use 18 decimals, but not all tokens do. Some stablecoins use 6 decimals. Some chain-specific or older tokens may use another value. If decimals are wrong, the displayed balance can look much too large or much too small.

If the wallet does not fill decimals automatically, check the verified explorer page or official documentation. Do not guess decimals for important tokens. If the wrong decimals were entered, the token display may be misleading even when the on-chain balance is correct.

Step 7: Add the token and check the balance

After the token details are verified, add the token to the wallet display. The wallet may now show the token balance if the address holds that token on the selected network. If the balance still does not show, check the wallet address, network, explorer, token transfer event, token decimals, wallet indexing delay, and RPC connection.

A missing balance after import does not always mean the token is gone. It may mean the wallet has not refreshed, the wrong network is selected, the token was sent to a different address, the transfer failed, or the token contract is not the expected one. For more troubleshooting, read Why Wallet Balance Does Not Show.

Step 8: Verify with a block explorer

The final check is the block explorer. A wallet interface can be delayed or incomplete, but a block explorer can show on-chain token transfers and token balances for the correct network. Search the wallet address or transaction hash on the correct explorer and confirm that the token transfer exists.

The explorer should match the same network as the wallet. An Ethereum explorer cannot confirm a BNB Smart Chain transfer. A Base explorer cannot confirm an Arbitrum transfer. The explorer, token contract, wallet address, and selected wallet network should all agree.

How to verify the token contract

Verifying the token contract is the most important part of adding a custom token. A fake token can copy a real token's name and symbol. A random token can appear in a wallet without the user asking for it. A scam page can tell the user to import a fake contract and then ask for approvals or signatures. The contract address is the anchor.

Use the official project source

The safest starting point is the official project source. This may be the official website, official documentation, official bridge page, verified social profile, official announcement post, or official app. Users should still verify the domain carefully because fake sites often copy branding and search-engine snippets.

Compare with a block explorer

After finding the contract, open it on the correct block explorer. Check whether the token name, symbol, decimals, contract address, holders, transfers, and verification status make sense. A verified contract is not a guarantee of safety, but an unverified or suspicious contract deserves extra caution.

Check the network

A token contract must be checked on the correct network. If a project has versions on multiple chains, each chain may have a different contract. A user importing a Base token into an Ethereum wallet view may see nothing even though the token exists on Base.

Avoid random sources

Do not copy token contracts from unknown comments, private messages, fake support accounts, unofficial mirrors, suspicious token lists, or search ads. Scammers often target users who are confused because a token does not appear in a wallet. They may offer a “sync,” “validate,” “refresh,” “rectify,” or “repair” page that asks for sensitive information.

Do not trust name, symbol, or logo alone

Token names, tickers, and logos can be copied. The same symbol can exist on many unrelated contracts. A wallet may show a familiar logo through a token list, but the contract still matters. The safer habit is to treat the contract address and network as the real identifier.

Understanding token decimals

Token decimals are often confusing because they affect how balances are displayed. A blockchain may store token balances as large integer values. Decimals tell the wallet where to place the decimal point for human-readable display. If decimals are wrong, the wallet may show a balance that looks incorrect.

For example, if a token uses 18 decimals, a raw on-chain balance may be displayed with 18 decimal places. If a token uses 6 decimals, the wallet should display it differently. A wrong decimal value can make the same raw amount look one trillion times larger or smaller depending on the mismatch.

Many popular EVM-compatible tokens use 18 decimals, but this is not a rule for every token. Some stablecoins and chain-specific assets use 6 decimals. Some tokens use 8, 9, or other values. The correct value should be checked from the contract, explorer, or official documentation.

What adding a custom token does not do

Many users misunderstand custom token import. Adding a token to a wallet display is not a blockchain transaction in most normal cases. It is usually a local wallet interface action. It helps the wallet show a token, but it does not change ownership on-chain.

• It does not create tokens: Importing a contract does not mint or generate a new balance.
• It does not recover lost funds: If funds were sent to the wrong address or wrong network, token import alone does not recover them.
• It does not approve spending: A normal token import should not give a contract permission to spend tokens.
• It does not require a seed phrase: Any custom token page asking for a seed phrase is dangerous.
• It does not prove the token is valuable: A wallet may show a token balance, but that does not prove liquidity, legitimacy, or market value.
• It does not prove the token is official: A fake token can still be imported and displayed.

Practical examples

Custom token issues become easier to understand through real-world style examples. These examples are educational and do not recommend any specific wallet, exchange, token, protocol, bridge, or claim page.

Example 1: Token received but not showing

A user receives a token from a friend. The transaction is confirmed on-chain, but the wallet does not show the balance. The user checks the transaction hash on the correct explorer and confirms that the token was transferred to the correct wallet address. The wallet simply does not display the token automatically. The user imports the verified token contract on the correct network, and the balance appears.

Example 2: Wrong network selected

A user receives a token on Polygon but opens the wallet on Ethereum. The wallet address may look similar because some networks use the same EVM-style address format, but the token exists on Polygon. The user switches to the correct network and imports the Polygon token contract, not an Ethereum contract.

Example 3: Fake token with copied symbol

A user searches for a token symbol and finds several contracts with the same name. One is official, and others are unrelated copies. If the user imports the wrong contract, the wallet may show a token with the same ticker but it will not be the intended asset. The user should compare the contract against official documentation and the correct network explorer.

Example 4: Token decimals display error

A user manually imports a token and enters the wrong decimals. The wallet shows a strange balance that appears too large or too small. The on-chain balance did not change. The display is wrong because the decimal setting is wrong. The user checks the contract decimals on the explorer and corrects the token display.

Example 5: Exchange withdrawal to a wallet

A user withdraws a token from an exchange to a non-custodial wallet. The exchange confirms the withdrawal, but the wallet does not show the token. The user checks the withdrawal network, transaction hash, receiving address, and token contract. If the transfer is confirmed to the correct address on the correct chain, the user may need to import the token contract manually.

Example 6: Bridge token version

A user bridges an asset to another network and expects the original token contract to appear. However, bridged assets may use a wrapped or network- specific contract. The user should check the bridge transaction, destination network, and official bridged token contract before importing anything.

Example 7: Scam token appears in wallet

A user notices an unknown token in a wallet. The token may have been sent without the user's request. Some scam tokens are designed to lure users into visiting a website, approving a contract, or signing a message. The user should not interact with suspicious tokens or follow links from token names. Simply seeing an unknown token does not mean the wallet is compromised, but interacting with the token can create risk.

What users should check

This checklist is useful before adding a custom token, importing a token contract, checking a missing balance, trusting a token symbol, connecting to a claim page, or accepting instructions from support.

• Wallet address: Confirm the exact public address and make sure the token was sent to that address.
• Network: Check the selected chain, chain ID if shown, gas token, explorer, and whether the token exists on that network.
• Token contract: Compare the token contract with an official source before importing the token or trusting a displayed symbol.
• Token decimals: Verify decimals from the explorer or official source if the wallet does not fill them automatically.
• Transaction hash: If a transfer happened, verify the hash on the correct block explorer.
• Token transfer event: Check whether the explorer shows an actual token transfer to the wallet address.
• Wallet request: Adding a token should not require seed phrases, private keys, broad approvals, or unclear signatures.
• Official source: Check the domain, documentation, app link, support route, and contract source before trusting token details.
• Secret information: Never share seed phrases, private keys, recovery phrases, passwords, or recovery codes.

Common wallet concepts

Wallet topics become easier once the core parts are separated. A beginner may see one wallet screen, but that screen can include public addresses, private keys, networks, balances, token contracts, transaction history, signatures, approvals, custom assets, and imported token lists. Each part has a different safety meaning.

Wallet address

A wallet address is the public destination used to receive funds and check on-chain activity. It can usually be shared, but it may reveal transaction history on public blockchains. Always copy it carefully and confirm the correct network before sending funds.

Private key and seed phrase

Private keys and seed phrases are secret access material. They should be stored carefully and never typed into websites, support chats, fake wallet forms, token claim pages, or recovery tools. If they are exposed, the wallet should be treated as compromised.

Network selector

The network selector controls which blockchain the wallet is viewing or using. A token on one network may not appear on another. When a balance, token, or transaction looks missing, the network selector is one of the first things to check.

Token contract

A token contract is the on-chain contract that defines a token on a specific network. It is more reliable than the token name, logo, or ticker. When adding a custom token, the token contract is the most important field.

Token symbol

A token symbol is the short label shown in a wallet, such as a ticker. It is useful for display, but it is not a secure identifier. Fake tokens can copy symbols, so users should verify the contract address.

Token decimals

Token decimals tell the wallet how to display the token's raw on-chain amount as a human-readable balance. Wrong decimals can make a balance appear incorrect without changing the actual on-chain amount.

Token import

Token import means adding a token contract to the wallet display. It does not send funds, approve spending, or create tokens. It only helps the wallet show a token that may already exist at the wallet address.

Wallet connection

Connecting a wallet usually shares a public address with an app and allows the app to request actions. It does not automatically mean the user has approved a transfer. However, users should still verify the official website before connecting.

Signature

A signature can be used for login, verification, permissions, or app-level authorization. Users should read the message before signing and avoid unclear signatures that claim to validate, synchronize, unlock, refresh, or restore a wallet.

Token approval

Token approval gives a spender contract permission to use a token up to a certain amount. It is different from simply importing a token. If an approval looks suspicious or is no longer needed, review How to Revoke Token Approval Safely.

Common mistakes

Wallet mistakes are common because many interfaces compress complex blockchain actions into short labels. A user may see a token symbol, wallet address, signature prompt, network name, token import field, transaction hash, or explorer page and assume it proves more than it actually proves. Safer wallet use starts with slowing down and checking the same information from more than one trusted place.

Mistake 1: Trusting a token name instead of a contract

Token names, tickers, and logos can be copied. The contract address and network are more reliable than the displayed token label. Before importing a token or trusting a token page, compare the contract with an official source.

Mistake 2: Importing the right token on the wrong network

A token contract belongs to a specific network. If a user imports an Ethereum contract while viewing BNB Smart Chain, it will not show the intended token. If a user imports a Base token while viewing Arbitrum, the wallet will not show the expected balance. Network and contract must match.

Mistake 3: Confusing token import with token recovery

Adding a custom token does not recover funds sent to the wrong address or wrong network. It only helps the wallet show a token that exists at the wallet address on the selected network. If a transfer went somewhere else, token import will not reverse it.

Mistake 4: Entering the wrong decimals

Wrong decimals can make the displayed balance look incorrect. This does not necessarily mean funds are missing or created. Check the decimals from the token contract, explorer, or official documentation.

Mistake 5: Following fake support instructions

Fake support accounts often target users whose tokens do not appear in a wallet. They may claim that the wallet needs to be validated, synchronized, rectified, refreshed, or restored. Be cautious if the fix requires seed phrases, private keys, remote access, unlock fees, broad approvals, or unclear signatures.

Mistake 6: Approving token spending instead of importing a token

A normal token import should not require a token approval. If a website asks the user to approve spending in order to display a token, stop and verify. Token approval is a permission action, not a display action.

Mistake 7: Clicking links from suspicious token names

Some scam tokens include website-like names or messages designed to attract clicks. A user may see an unknown token in a wallet and visit the linked site. This can lead to phishing, malicious approvals, or seed phrase theft. Do not trust a link just because a token appeared in the wallet.

Mistake 8: Assuming wallet display proves value

A wallet may display a token balance, but that does not prove the token has liquidity, market value, official status, or safe transfer behavior. Some tokens are spam, fake, illiquid, or designed to trick users into interacting with unsafe contracts.

When to be extra careful

Some wallet actions deserve extra caution because they can expose funds, permissions, wallet history, recovery material, or future token access. Slow down when a page asks you to import a custom token, connect a wallet, sign a message, approve token spending, bridge assets, claim rewards, join a presale, import a suspicious contract, or follow a support link from social media.

• Before importing a token: Confirm the contract from an official source and make sure the selected wallet network matches.
• Before trusting a token balance: Check whether the token contract is official, liquid, transferable, and expected.
• Before receiving funds: Confirm the exact wallet address, token, and network with the sender.
• Before sending funds: Check the destination address, network, gas token, transaction preview, and explorer result after confirmation.
• Before connecting a wallet: Verify the official website, domain spelling, app purpose, and whether the connection is necessary.
• Before signing a message: Read the message content and avoid unclear wallet validation, synchronization, refresh, or repair requests.
• Before approving token spending: Check the token, spender contract, network, amount, and whether the approval matches the intended action.
• Before following support instructions: Confirm the support route from the official website and never reveal secret wallet information.

How to verify wallet activity

A wallet screen is useful, but important actions should be verified through the correct block explorer when possible. The explorer can show whether a transaction was pending, confirmed, failed, dropped, or replaced. It can also show sender and recipient addresses, token transfer events, contract interactions, gas used, timestamps, token contracts, and sometimes token holder information.

1. Copy the wallet address or transaction hash: Use the exact value shown in the wallet, exchange withdrawal page, bridge page, claim page, or app.
2. Open the explorer for the correct network: Make sure the explorer matches the chain where the token or transaction should exist.
3. Check the address or transaction page: Review status, timestamp, sender, recipient, token transfer, gas, and contract interaction.
4. Open the token contract page: Compare the token contract, symbol, decimals, holders, transfers, and source information with official references.
5. Compare with the wallet: If the wallet and explorer show different information, check network selection, token import, decimals, RPC delay, wallet interface delay, and indexing delay.
6. Confirm the final result: Do not rely only on a popup. Verify whether the intended balance, transfer, approval, or transaction result actually happened.

Troubleshooting: token still does not appear

If a token still does not appear after importing it, slow down and check the basic facts again. Most missing token problems come from address mismatch, network mismatch, contract mismatch, token decimals, wallet indexing delay, RPC delay, or a transaction that did not actually transfer the token.

Check the selected network again

The wallet must be on the same network as the token contract. If the token exists on Base, the wallet should be viewing Base. If the token exists on BNB Smart Chain, the wallet should be viewing BNB Smart Chain. If the wallet is on the wrong network, the token will not display correctly.

Check the receiving address

Make sure the token was sent to the wallet address being viewed. A single copied character mistake can send funds to a different address. Some users also accidentally check a different wallet account inside the same wallet app.

Check the transaction status

A pending, failed, dropped, or replaced transaction may not create the expected token balance. Search the transaction hash on the correct explorer and confirm whether the token transfer actually succeeded.

Check the token transfer event

Some transactions interact with contracts but do not transfer the expected token to the user's wallet. On the explorer, review the token transfer section, logs, or token balance changes. A successful transaction hash alone does not always mean the expected token was received.

Check token decimals

If the token appears but the balance looks wrong, decimals may be incorrect. Compare the decimals with the explorer or official documentation. If the wallet allows editing token details, correct the decimals or remove and re-add the token using verified details.

Check wallet indexing or RPC delay

Wallet interfaces can be delayed. The blockchain may show the transfer before the wallet UI updates. Users can refresh the wallet, change RPC endpoints if they understand the risk, or wait for indexing. The explorer is often a better source for final on-chain confirmation than the wallet display.

External learning references

For broader educational context, users can compare this guide with official documentation and neutral education pages from established ecosystem sources. Always check that a link is official before relying on it, and never enter private keys or seed phrases into any page reached from a search result, advertisement, direct message, or unofficial mirror.

• Ethereum.org: Wallets — general explanation of Ethereum wallets, wallet responsibility, and self-custody basics.
• Ethereum.org: ERC-20 Token Standard — technical educational overview of the ERC-20 token standard used by many EVM-compatible tokens.
• MetaMask Support — wallet support material that includes token display, custom token, and wallet safety topics.
• Ledger Support — educational support material about wallet safety, token display, and hardware wallet usage.
• Trezor Learn — educational material about self-custody, hardware wallets, backups, and wallet safety concepts.

These external links are included for educational comparison only. Eonwell does not control external sites and does not recommend any specific wallet, token, exchange, bridge, explorer, hardware wallet, custody service, or protocol.

FAQ

What does it mean to add a custom token?

Adding a custom token means entering a token contract into a wallet so the wallet can display that token on the selected network. It does not create tokens, move funds, or approve spending. It only changes what the wallet interface shows.

Why is my token not showing in my wallet?

A token may not show because the wrong network is selected, the token contract has not been imported, the wallet address is different, the transaction failed, the wallet interface is delayed, or the token contract is not the expected one. For more detail, read Why Wallet Balance Does Not Show and Why Token Does Not Appear in Wallet.

Where do I find the token contract address?

The token contract should be found from an official source, such as the project's official website, documentation, verified explorer page, or trusted announcement. Avoid copying contracts from random comments, direct messages, search ads, or unofficial support accounts.

Can a fake token have the same name as a real token?

Yes. Token names, tickers, and logos can be copied. The contract address and network are more reliable identifiers than the display name. Always compare the contract with an official source before importing or trusting a token.

Does adding a custom token cost gas?

In many wallet interfaces, adding a custom token for display does not require an on-chain transaction and does not cost gas. If a page asks for gas, token approval, a signature, or a seed phrase just to display a token, stop and verify what the request actually does.

Does importing a token approve spending?

A normal token import should not approve spending. Token approval is a separate permission that allows a spender contract to use a token. If an approval looks suspicious or is no longer needed, read How to Revoke Token Approval Safely.

Do I need my seed phrase to add a custom token?

No. A normal custom token import should not require a seed phrase, private key, recovery phrase, or secret phrase. If a website or support account asks for secret wallet information, treat it as unsafe.

What are token decimals?

Token decimals tell a wallet how to display the token's raw on-chain balance as a human-readable amount. If decimals are wrong, the displayed balance can look incorrect even when the actual on-chain balance is unchanged.

Why does my custom token balance look too high or too low?

The token may have been imported with the wrong decimals, or the wallet may be reading token details incorrectly. Check the token contract page on the correct explorer and compare the decimals with official documentation.

Can I add any token contract to my wallet?

Many wallets allow users to add custom token contracts, but that does not mean every token is safe or official. A wallet may display a fake, spam, illiquid, or malicious token. Users should verify contracts before trusting displayed balances.

Can adding a custom token recover funds sent to the wrong network?

No. Adding a custom token only affects wallet display. It does not move funds between networks or reverse transfers. If funds were sent on the wrong network, users should first identify the destination address, network, transaction hash, and whether the receiving wallet or platform supports that network.

Can adding a custom token recover funds sent to the wrong address?

No. If funds were sent to the wrong address, importing a token into a different wallet cannot recover them. The token must actually exist at the wallet address being viewed on the selected network.

Why does the explorer show my token but my wallet does not?

The wallet may not have imported the token contract, may be on the wrong network, may have indexing delay, or may need a refresh. If the correct explorer shows the token at the correct wallet address, custom token import may help the wallet display it.

Why does my wallet show a random token I never bought?

Some tokens are sent to wallets without the user's request. These may be spam tokens, scam tokens, promotional tokens, or unrelated assets. Do not follow links from unknown token names or approve contracts just because a token appears in the wallet.

Should I hide or remove unknown tokens?

Hiding or removing an unknown token from the wallet display may reduce clutter, but it does not remove the on-chain token from the address. Avoid interacting with suspicious tokens unless you understand the risk and can verify the contract.

Can a custom token be dangerous?

Simply displaying a token is usually not the dangerous part. The risk often comes from following links, approving spending, signing unclear messages, or interacting with malicious contracts connected to the token. Treat unknown tokens with caution.

What should I check before importing a token from an airdrop?

Check the official airdrop source, token contract, selected network, claim instructions, wallet request, and whether any approval or signature is being requested. Do not enter a seed phrase to claim or import a token. For safety context, read How to Avoid Crypto Scams.

What should I check before importing a bridged token?

Check the source network, destination network, bridge transaction, token contract on the destination chain, and whether the bridged asset is the expected version. Bridged tokens may use different contracts from the original token.

Is a token contract the same as a wallet address?

No. A wallet address is usually a user's public address for receiving and sending funds. A token contract address identifies the smart contract that defines a token on a network. Both are public, but they are used for different purposes.

What is the safest way to add a custom token?

The safest pattern is to confirm the wallet address, select the correct network, get the token contract from an official source, verify it on the correct explorer, check symbol and decimals, add the token, and confirm the balance through the explorer. Never reveal seed phrases or private keys during this process.

Related concepts

This wallet topic connects to several nearby crypto concepts. Understanding these pages can help readers move through the Eonwell archive in a safer order, especially if they are learning how wallets, addresses, private keys, networks, token contracts, transactions, explorers, signatures, approvals, and Web3 apps fit together.

• What Is Cryptocurrency?
• What Is Blockchain?
• How Crypto Wallets Work
• What Is a Crypto Wallet Address?
• Wallet Address vs Private Key
• Why Wallet Balance Does Not Show
• Hot Wallet vs Cold Wallet
• Custodial vs Non-Custodial Wallet
• Hardware Wallet vs Multisig
• What Is a Blockchain Network?
• Why Wallet Network Matters
• How dApps Connect to Wallets
• How Crypto Transactions Work
• Why Token Does Not Appear in Wallet
• Why Is My Wallet Balance Not Showing?
• How to Fix Token Decimal Display Error
• Why Token Approval Is Needed
• How to Revoke Token Approval Safely
• What to Do After Clicking a Suspicious Crypto Link
• What to Do If Seed Phrase Was Exposed
• What to Do If Private Key Was Exposed
• How to Check Official Links
• How to Avoid Crypto Scams

Summary

Adding a custom token to a crypto wallet means importing a token contract so the wallet can display that token on the selected network. It does not create tokens, move funds, approve spending, bridge assets, or recover tokens sent to the wrong address. The most important checks are the wallet address, selected network, official token contract, token decimals, transaction hash, token transfer event, and correct block explorer. Token names, symbols, and logos can be copied, so users should not trust a token only because it looks familiar. A normal custom token import should never require a seed phrase, private key, recovery phrase, broad approval, or unclear signature. If a wallet balance still does not appear, the issue may involve network selection, token import, decimals, wallet indexing, RPC delay, or a transfer that did not actually reach the address.

The safest wallet habit is to verify before acting. Check the wallet address, selected network, transaction hash, token contract, token decimals, wallet request, official source, and final explorer result before sending funds, importing tokens, signing messages, approving spending, or connecting to a site. This reduces the chance of using the wrong network, trusting a fake contract, exposing secret wallet information, approving an unsafe spender, or mistaking a display issue for an on-chain balance issue.

Eonwell does not recommend any specific wallet, token, exchange, protocol, bridge, explorer, hardware device, custody service, or transaction. This page is for neutral crypto education only.