For some tokens, chain.report cannot find price information.
This can have two consequences:
a) You will see a warning in the relevant transaction, displayed as follows:
b) The token is interpreted as the next closest token through a heuristic. Example: The heuristic reads SOLI as Sol (Solana). This can be exactly right. However, it could also mean that you intended to process an unknown token named "Soli." In this case, the price information is incorrect, and manual adjustments are required.
Missing prices or unknown tokens can have the following reasons:
Missing price information on CoinmarketCap or the Dexes
If chain.report cannot determine a price for a token (then defined as unknown).
The relevant price information is (not yet) available on CoinMarketCap or the DeFiChain Dex. This could be because CoinMarketCap only started listing your token from a certain point in time. In this case, you would need to enter the relevant price information in the field at the bottom right.
Mapping of native tokens
It is a staking token like XTZ.S or csETH or stETH. These are not yet supported by chain.report.
Based on the following tax argumentation, such tokens are often recorded as native tokens:
Example:
* WBTC is always recorded as BTC
* csETH is always recorded as ETH
* ...
If an automatic conversion of your desired token is not yet supported, you can request this from chain.report support or, in this case, you could edit the transaction and, for example, change csETH to ETH if you follow the following tax argumentation:
But also keep in mind that there should be no transfer, for example, from dBTC to BTC. This transaction will be ignored by chain.report.
If you receive a warning about an unknown token (neither known by CoinMarketCap nor the Dex), you can only enter the price once. This is necessary to ensure that a tax report cannot be manipulated and to maintain the integrity of the report. If you want to change a price multiple times, you would need to recreate the transaction or the wallet.
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 suitable CSV file? If so, please upload it as well.
If you have identified errors clearly, 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 don't know exactly 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.