The price of my token is not known, or the token is not supported

For some tokens, chain.report finds no price information.

This can have two consequences:

a) You are shown a warning in the corresponding transaction, which is displayed as follows:

b) As part of a heuristic, the token is interpreted as the next most suitable token. Example: Through the heuristic, SOLI is read as Sol (Solana). That can be exactly right. But it can also mean that you really wanted to process an unknown token named "Soli" here. In this case, the price information is not correct, and manual follow-up is required.

Missing prices or unknown tokens can have the following causes:

1. Missing price information on CoinMarketCap / CoinGecko or the DEXes

   chain.report cannot determine a price for a token (then defined as unknown).

2. On CoinMarketCap / CoinGecko or on the DeFiChain DEX, the corresponding price information is not (yet) available. This can, for example, be because CoinMarketCap / CoinGecko only listed your token from a certain point in time. For this case, you would have to enter the corresponding price information in the field at the bottom right.

3. Mapping of native tokens

   This is a staking token such as XTZ.S or csETH or stETH. These are not yet supported by chain.report.

   On the basis of the following tax reasoning, corresponding tokens are often recorded as the native token:

   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 reasoning:

   But also keep in mind that there must then no longer be a transfer, for example from dBTC to BTC. This transaction is ignored by chain.report accordingly.

In the case of a corresponding warning for an unknown token (known neither through CoinMarketCap / CoinGecko nor the DEX), you can enter the price only once. This is necessary so that a tax report cannot be manipulated and in order to ensure the integrity of the report. If you want to change a price more than once, you would have to create the transaction or the wallet again.

You have checked these points and you still see an error in chain.report?
Then we need a precise error description in which the error can be identified on specific transactions or other points. Information would include, for example:

1) Which transaction(s) are involved? (date, time, transaction type, token, amount, ...). Please give a single example if possible.

2) Where do you see an error?

3) Can a screenshot illustrate this?
4) Is there a suitable CSV file? Then please upload this as well.

If you were able to identify the error this 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 do not know exactly why?
Example: You cannot resolve warnings?
Example: There are balance discrepancies in the wallets.
Please understand that we cannot take on a portfolio analysis for Non-Professional-User here in order to look for potential errors. This option exists for the Professional package. A good starting point would be our FAQ - there you will find answers to these three points and to most other questions.