It's possible that the asset recorded for your transaction isn't the one you expected. There could be several reasons for this, which don't necessarily indicate an error.
Here is a checklist of possible causes:
1. There is a symbol with the same name for the asset. chain.report will prioritize the asset with higher CoinmarketCap priority.
Example:
You traded with the asset "Solcoin," which uses the symbol SOL. However, chain.report will prioritize Solana.
Due to the data situation, only the text "SOL" might be provided by the exchange, necessitating prioritization.
2. The token is unknown
chain.report maintains its token list according to CoinmarketCap's list. If you chose a token outside this list (e.g., a MemeCoin), a custom asset will be created, and a note about missing price information will appear in the transaction. You will need to add the price in the note section of the transaction.
Learn more about determining price data in chain.report in this article.
3. The exchange uses an inappropriate name or staking token
An exchange might use an unusual name for the token in the data.
Example:
The exchange provides XXBT instead of BTC (Bitcoin). In the transaction, an unknown token XXBT is read.
Staking Example:
Staking tokens are often listed under different names on many exchanges. For instance, DOT might be listed as a staking token with DOT2 or DOT.S.
For many exceptions, chain.report recognizes these special names and resolves them to the correct asset for you.
4. A custom asset was prioritized
If you manually created your own custom asset or it was created for you due to the absence of this token, it will be prioritized over a token with the same name. This might not match your expectations. If you want to remove a specific custom asset from your account, please delete all wallets containing this token. If the token is no longer used, custom assets in chain.report are deleted every 12 hours.
5. Your asset is affected by a token swap and is no longer available at the time of the transaction.
Example:
An exchange or your entry includes the token MATIC in September 2025. All occurrences of MATIC have been replaced in a token merge. chain.report will handle this replacement for you.
Learn more about token merges in this article.
6. A smart contract was used in your transaction.
Smart contracts need to be individually supported by chain.report. There is a default detection. If your applied smart contract falls outside this, there is a possibility that a transaction was not read or was read incorrectly. This can also affect the asset read.
Learn more about reading smart contracts in this article.
Recommended actions:
For missing price data, you can add the price in the expanded transaction. To determine prices, you can research with your provider, on coingecko.com, or on coinmarketcap.com.
If the expected token was not recognized, the above checklist shows reasons that do not result from an error in chain.report. You then have the option to simply edit the asset in the expanded transaction:
Have you checked these points and still see an error with chain.report?
Then we need a precise error description, where the error can be identified in specific transactions or other points. Information could include:
1) Which transaction(s) are involved? (Date, time, transaction type, token, amount, ...). Please provide a single example if possible.
2) Where do you see an error?
3) Can a screenshot clarify this?
4) Is there a relevant CSV file? Please upload it as well.
If you could clearly identify errors, please send us the data via the support chat on the website.
If you cannot clearly identify the error or its cause:
Example: The tax burden is too high, but you're not sure why?
Example: You can't resolve warnings?
Example: There are balance discrepancies in the wallets.
Please understand that we cannot perform a portfolio analysis for non-professional users to search for potential errors. This option is available for the Professional package. A good starting point would be our FAQ - there you will find answers to these three points and most other questions.