There is a possibility that an exchange might swap a large number of your tokens for a different amount of another token. The token is thus renewed and transferred. This process is not considered taxable in chain.report, so the original purchase value is used for any future sale.
Typically, merge data is not available through the exchange's API or CSVs. Therefore, you need to manually create a token merge transaction here. You can use the template or the web buttons for this.
💡 Example:
On 07/18/25, 100 BEST were exchanged for 491 VSN via token merge on the exchange for you. Typically, merge data is not available through the exchange's API or CSVs. Therefore, you need to manually create a token merge transaction from 100 BEST to 491 VSN for 07/18/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 and even CoinMarketCap temporarily or permanently removing the token from their tracker. Additionally, there was a token swap to Terra Luna Classic (LUNC).
The result is: There is no price information, or incorrect prices are loaded due to different LUNA tokens.
If there is no price for the respective tokens in chain.report, a warning will be displayed on the corresponding transaction. When you expand it, you have the option to correct the price. For example, you can determine the LUNA price in the following ways:
Determine the price in a trade through the counter-asset. If you acquired 10,000 LUNA for 50 EUR, the LUNA price would have been 50 EUR / 10,000 = 0.0005 EUR.
Determine the price in EUR at the time of the transaction on Trading-View via a corresponding ticker of an exchange that has the price available.
It is also important to ensure that the correct asset, LUNA or LUNC, is meant. We have recorded the token swap between LUNA and LUNC on 05/11/22.
However, it is important to note that LUNA and LUNC can continue to coexist because LUNA is the new "real" LUNA, and LUNC is the old LUNA, thus Luna Classic. Unfortunately, exchanges do not consistently name LUNA and LUNC before and after this swap date as one might assume with this logic.
It is therefore essential that you have an understanding of the LUNA and LUNC tokens regarding their use and meaning. Only then can you change the token in your transactions so that the correct LUNA is used - with the correct price information.
By the way: The same issue applies to ERD and EGLD, as there is also a fixed swap date here, and both tokens can coexist after this date.
Token Swaps with Swap Date: For example, MCO becomes CRO
Some tokens have a fixed swap date as described. For example, MCO becomes CRO from a certain date. We automate this change for you - with a conversion factor. We have to do this alone because of the CoinMarketCap prices. If you enter MCO after the swap, they will be directly recorded as CRO. Before the swap, CRO will automatically be recorded as MCO. Only in this way is price information available.
Unfortunately, some exchanges handle this issue differently, so there can be quantity differences due to the factor, just like with LUNA and LUNC. Here, unfortunately, our hands are tied. Here too, your understanding and processing are necessary.
Token Swaps after which CoinMarketCap no longer provides price data:
There is a possibility that one token is completely replaced by another. An example of this is FTM, which was replaced by S (Sonic).
Either way, you can now check on coinmarketcap.com which time periods are available for prices of both tokens. Since, unfortunately, no price is available for FTM in the example, we automatically switch the token for you to WTFM (the wrapped token with the same price information).
Have you checked these points and still see an error in chain.report?
Then we need a precise error description, where the error can be identified in specific transactions or other points. Information would 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 illustrate this?
4) Is there a suitable CSV file? If so, please upload it as well.
If you were able to 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 don't know exactly why?
Example: You can't resolve warnings?
Example: There are balance discrepancies in the wallets.
Please understand that we cannot conduct 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.