There are always notifications when data is missing. These are not system errors, but rather indications that missing data still needs to be explained.
In the report overview, you can see the number of notifications for a calendar year:
Important: Please only consider the number of your notifications after you have entered all your wallets and exchanges into chain.report without exception - otherwise, notifications about missing data are exactly the result of this.
Notifications can also arise later
- for example, due to new data foundations from exchanges (new features, less data, and many other possibilities)
- tax law might have been adjusted.
- on Dexes like the DefiChain, the environment is highly dynamic.
There are 4 types of notifications:
1. The origin of assets in a transaction is unknown
2. The destination of a withdrawal is unknown
3. The price of assets in a transaction is unknown
4. A smart contract was not recognized and leads to a faulty transaction
1. The origin of assets in a transaction is unknown
The source of funds used may be missing in your transaction. chain.report cannot recognize the original acquisition cost of this asset. Therefore, chain.report sets the acquisition price of this asset to €0 for you. A later sale can thereby increase the tax burden.
Warning: Please avoid using the buttons "Mark as bank deposit", "Mark as airdrop", or "Ignore" if you are not sure that this was exactly the correct purpose. You could potentially also unintentionally increase your tax burden here.
The main cause is likely that you have not entered the source wallet from which the funds come. If you enter this later, the notification will resolve itself. However, incomplete data and missing transactions from exchanges are common and need to be updated. You can see the limitations of an exchange's API in the dialog when setting up the wallet. A checklist to check for causes of missing transactions can be found in this linked article.
To trace the original acquisition, you can take a closer look at the sales list by expanding the transaction. Keep in mind that, for example, the sorting order of an asset per wallet is FIFO (First in First Out).
Here you will find a guide to handling notifications of missing sources:
2. The destination of a withdrawal is unknown
If, for example, the target wallet of a transfer is unknown, we must assume a sale. chain.report cannot recognize whether the asset is still in your possession or if you have sold it without a known target wallet.
chain.report will therefore defensively assume a taxable sale - which, if untreated, can increase your tax burden
Warning: Please avoid using the buttons "Mark as payment" or "Ignore" if you are not sure that this was exactly the correct application. You could also unintentionally increase your tax burden here.
The most likely solution is that you have not entered the target exchange of this withdrawal. You should now catch up on this. If you have actually sold the assets here, you can mark the transaction as a payment.
Here you will find a guide to handling notifications for missing target wallets of withdrawals:
3. The price of assets in a transaction is unknown
In transactions, it can happen that there is no price information available, which is required for profit calculation. chain.report generally uses prices from coinmarketcap.com.
Solution 1:
You can check if the price at the requested time is available on coinmarketcap.com or coingecko.com to add it.
Solution 2:
Check that the correct asset was used. If an exchange, for example, provides a transaction with the asset $BEER instead of BEER, there will be no price information for BEER. So check if the correct asset was recorded and potentially change the asset when editing the transaction.
Further information on price determination by chain.report can be found in this linked article.
Here you will find a guide to handling notifications for missing prices:
4. A smart contract was not recognized and leads to a faulty transaction
Connected to a native blockchain (like Ethereum or Solana), your wallet (e.g., MetaMask) can execute smart contracts. Many of these smart contracts are understood by chain.report and are evaluated correctly for tax purposes.
However, particularly unknown or exotic smart contracts cannot be read correctly without individual implementation. If the automatic base recognition cannot be applied, the result is often a faulty transaction. Faulty transactions can be, for example:
1. A trade where, for example, the entry or exit is missing
2. Other income where only an exit was read, but not an inflow
3. Transactions where too much data was stored
4. .. other possible combinations
You can often recognize this by reviewing the transaction. Additionally, the explorer link and the tooltip of the transaction are helpful, as they can indicate what really happened in this transaction - because you now need to manually represent this.
Logging into the exchange can also help you find out which product you used here. Once you've determined what the execution actually included, you can correct the transaction as follows:
1) Edit the transaction using the "Correct Transaction" button
2) Delete the transaction and re-upload it using a template. This has the advantage of providing you with a backup afterward.
A more detailed description of the corresponding notice and how to fix it can be found in this YouTube video:
Need professional support?
Check out our consulting packages in the Support Tab and inquire about an individual portfolio consultation.
Have you thoroughly checked these points and still see an error on chain.report?
Does this mean you've found a specific error and not a warning you can't explain?
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 clarify this?
4) Is there a relevant 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're not sure 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'll find answers to these three points and most other questions.