These are token swaps or token merges - and this is what you need to understand for them

It is possible that an exchange exchanges a quantity of your tokens for a different quantity of another token. The token has thus been renewed and transferred. This process is not treated as taxable in chain.report, so that on a later disposal the original acquisition value is used.

As a rule, merge data is not available via the API or the CSVs of the exchange. You therefore have to create a token merge transaction manually here. You can use the template or the web buttons for this.

💡 Example:

On 18.07.25, 100 BEST were exchanged by the exchange for you into 491 VSN via token merge. As a rule, merge data is not available via the API or the CSVs of the exchange. You therefore have to manually create a token merge transaction from 100 BEST to 491 VSN here for 18.07.25. You can use the template or the web buttons for this.

The corresponding transaction type for this is the token merge:

💡 Example:
In 2022, the crypto token LUNA experienced an unprecedented downward price correction. This led to many exchanges, but also CoinMarketCap / CoinGecko, removing the token from the tracker temporarily or completely. In addition, there was a token swap into Terra Luna Classic (LUNC).

The result is: There is no price information, or incorrect prices are loaded because of different LUNA tokens.

If no price is available for the corresponding tokens in chain.report, a warning is displayed to you on the corresponding transaction. When you expand it, you then have the option to correct the price afterwards. You can, for example, determine the LUNA price in the following way:

1. You determine the price in a trade via the counter-asset. If, for example, you acquired 10,000 LUNA for 50 EUR, the LUNA price would have been 50 EUR / 10,000 = 0.0005 EUR.

2. You determine the price in EUR at the time of the transaction on TradingView via a corresponding ticker of an exchange that has the price available.

It is also important that the correct asset, LUNA or LUNC, is meant. We have entered the token swap between LUNA and LUNC on our side on 11.05.22.
It is important, however, that LUNA and LUNC can continue to coexist, because LUNA is the new "real" LUNA, and LUNC is the old LUNA and thus Luna Classic. Unfortunately, the exchanges do not name LUNA and LUNC before and after this swap date consistently in the way that would be assumed with this logic.

It is therefore essential that you have an understanding of the LUNA and LUNC tokens with regard to their use and meaning. Only then can you change the token in your transactions so that the correct LUNA is used - that is, with the correct price information.

By the way: The same issue is also applicable to ERD and EGLD, since there is also a fixed swap date here and both tokens can also coexist after this date.

Token swaps with a swap date: e.g. MCO becomes CRO
Some tokens, as described, have a fixed swap date. For example, from a certain date MCO becomes CRO. We automate this change automatically for you - namely with a conversion factor. We have to do this if only because of the CoinmarketCap / CoinGecko prices. If you enter MCO after the swap, these are then carried directly as CRO. Before the swap, CRO is automatically carried as MCO. Only in this way is price information available.

Unfortunately, some exchanges treat the topic differently, so that, exactly as with LUNA and LUNC, quantity differences can arise because of the factor. Unfortunately, our hands are tied here. Here too, editing and an understanding on your part are necessary.

Token swaps after which CoinmarketCap / CoinGecko no longer provides price data:
It is possible that one token is replaced completely by the other. An example of this is FTM, which was replaced by S (Sonic).
Either way, you can now check on coinmarketcap.com / CoinGecko which time periods are available for prices of both tokens. Since, in the example of FTM, unfortunately no prices are available anymore, we automatically change the token for you to WTFM (the wrapped token with the same price information).

Have you 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 be, for example:

1) Which transaction(s) does it concern? (Date, time, transaction type, token, quantity, ...). If possible, give a single example.

2) Where do you see an error?

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

If you have been able to identify errors 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 here that we cannot take on a portfolio analysis for non-professional users here in order to look for potential errors. This option exists for the Professional package. A good starting point here would be our FAQ - there you will find answers to these three points and to most other questions.