Adding a custom token: Four checks beyond its name and logo

Adding a custom token changes what the wallet displays. It does not establish that the asset is the project you intended, that it has a reliable price or that you can sell it. Verify the network and complete contract address, then separate display configuration from any signing or spending request.

Adding a custom token changes what the wallet displays. It does not establish that the asset is the project you intended, that it has a reliable price or that you can sell it. Verify the network and complete contract address, then separate display configuration from any signing or spending request.

A token’s practical identity
NetworkWhich chain is being read?
ContractWhich exact token contract?
UnitsHow is raw quantity displayed?

A familiar name and logo are not proof of contract identity or market value.

BTKWIN.COM · EDUCATIONAL EXAMPLE

What adding a token actually does

For common contract-based tokens, a contract manages token balances and supported operations. The wallet reads relevant data to show a quantity and label for your account. Supplying a contract address tells the interface which token to display; it does not create a balance on the network.

If you already hold the token but the asset list omits it, adding the correct details may make it visible. If a transfer never reached the account, filling in import fields will not recover it. Distinguish a display issue from a transfer or account-identity issue before changing settings.

Also distinguish the network’s native currency from a token managed by a contract. Their display and fee requirements can differ. Use documentation appropriate to the asset rather than applying custom-token instructions to every kind of coin.

1. Match the network and complete contract

Start from a project channel you have independently established or reliable transaction data. Compare the full contract address on the intended network with that reference. A search result containing the right name can still point to a different contract using a copied logo.

When an asset exists on multiple networks, verify each version separately. A shared label does not prove identical backing, redemption rights or administrative control. The network and contract together are a more useful identity reference than a ticker alone.

Record the source of your identification. A popular list can be a clue, but moving an address between lists does not establish that it belongs to the asset actually sent to your account. Automatic detection in a wallet does not remove this identity question either.

2. Understand name, symbol and decimals

A wallet may retrieve some display metadata automatically or require supported fields to be entered. The ERC-20 specification describes name, symbol and decimals as optional metadata methods. Their role is presentation, and familiar values are not a certificate of authenticity.

Decimals translate a raw balance into readable units. Do not change them arbitrarily until a number resembles what you expect. A wrong interpretation can produce a misleading display without changing the actual balance recorded by the contract.

If the data is unclear, revisit the contract and reliable documentation. Do not fill gaps with guesses to make the screen look consistent. An attractive display is not evidence that the units are right, and a surprising number is not by itself evidence of another transfer.

An arithmetic example of display units

Suppose an educational token example has a raw quantity of 3,500,000 and the correct decimal setting is 6. Dividing by one million gives 3.5 displayed units. These are hypothetical quantities, not a current balance or quote for a named asset.

If the same raw quantity were interpreted with 18 decimals, the interface would show 0.0000000000035 units. No assets moved because the display interpretation changed. Correcting the unit setting is different from sending more funds or buying another similarly named token.

Confirm identity before fixing units. Otherwise you may accurately format the balance of the wrong contract. Once identity is established, compare the expected display method with the product’s supported behavior and a suitable independent data source.

3. Separate visibility from price, liquidity and rights

A token can show a large quantity without a reliable fiat valuation. A displayed price can also come from a source that does not demonstrate an executable sale for your intended amount. Multiplying the quantity by that number does not guarantee withdrawable proceeds.

Confirming the contract first answers which token you are reading. It is not a comprehensive assessment of administrative powers, transfer restrictions, liquidity or holder rights. A correct import can coexist with significant product or market risk.

If you are investigating a claimed payment, ask for the network and transaction identifier. Review actual destination and execution outcome, then the current balance. A screenshot supplied by another party is not a substitute for determining what occurred on the appropriate network.

4. Distinguish display from spending permission

Reading and displaying a balance is not the same action as granting a contract permission to spend. If a token-display task produces an approve or other authorization request, inspect the request’s actual purpose before accepting it. Buttons on the same page need not represent one indivisible operation.

Some requests produce an off-chain signature without charging gas immediately. Absence of an immediate fee is not a complete safety test. Compare the requested authority with the task you intended to perform, and stop if you cannot explain the connection.

Never provide recovery words or private keys to a service claiming it must synchronize a token balance. Public identity and transaction information are generally the appropriate starting points for a display investigation. A request for spending secrets changes the nature of the task.

What each piece of information can establish

InformationUseful forDoes not establish alone
Name and logoVisual organizationAuthenticity
Network and contractSpecific token identityProject quality or value
DecimalsReadable interpretation of raw unitsUnit price or saleability
Displayed priceSource-dependent estimateExecution at that price and quantity
Asset-list importLocal visibilityRecovery of a wrong transfer or spending permission

What if an unfamiliar token appears?

Unsolicited tokens or promotional messages can appear without you requesting them. Their presence is not an instruction to visit a site promising redemption or unlocking. Investigate identity without granting permissions simply because the label suggests a reward.

Hiding a token is usually an interface action, not deletion of its on-chain existence. Review the product’s supported hide or report options. You do not need to transfer an unfamiliar asset merely to tidy the screen, particularly if that would lead you into an unexplained signing flow.

Confirm whether the display problem is resolved

Compare the account, network, contract and quantity against an appropriate data source. Then distinguish any remaining mismatch: wrong identity, wrong units, synchronization delay or unavailable pricing. Each calls for a different next question.

Preserve the non-secret facts needed for official support and keep recovery material out of diagnostic forms. Our empty wallet guide explains why matching the account precedes adjusting the asset list. A successful import is evidence about display, with the limits described above.

Continue reading

English content and examples reviewed: 27 October 2026. Read the Arabic edition.

تامر طعمه
تامر طعمه
Articles: 387