Bug reports (public)

I bought all of my ETH years ago, yet the bulk (67%) isn't supposed to mature until late this year (according to the ASSET MATURITY feature). I did not buy ETH last year, and there are also no such trades in my transactions. What I did do a lot last year is use my existing ETH to buy smaller altcoins. I don't see how that could be misinterpreted as making large ETH purchases. - The same goes for SOL. I've owned several SOL for years, yet not a single SOL shows up as long term... I FOUND THE ANSWER TO THIS PROBLEM. SEE COMMENT BELOW.

On the new Asset Maturity page, I'm seeing coins that I no longer own or that were received as spam. In the dashboard overview, these are automatically hidden — it would be great if the same applied to Asset Maturity, or if we had the option to hide them manually. Otherwise, it gets distracting.

I have trades done in the same second (differ my milliseconds). Koinly often imports them in the wrong order causing "missing purchase history" Workaround I have to fix the order of the transactions manually, moving the later transaction 1 min to the future.

I've noticed the following behaviors: Occasionally, there is an error (!) shown for an asset in the dashboard, but no error for the same asset in the wallet view. Occasionally, there is an error (!) shown for an asset in the wallet view, but no error for the same asset in the dashboard view. There is an error (!) shown for an asset in the wallet view and the dashboard view, but the modal reports different error values. All of this makes it extremely difficult to know which error is the correct one to resolve. Worse, it makes me lose trust that the software is performing the right calculations at all. It seems quite basic to me that the errors should be consistent. If there is a good reason why they shouldn't match in some cases, then I'd expect an easy to access explanation as to why that can be the case to establish trust, otherwise it just looks like a bug.

Bitstamp allows users to purchase crypto directly with PayPal. My dashboard shows an incorrect EUR balance. The amount shown in the error is exactly equal to the amount of fees taken from purchases made directly with PayPal. It seems these transactions count 2x the fee. Example: A 100 EUR fee from a PayPal purchase is counted as a 200 EUR fee. To fix this, I need to do one of the following: 1) Add a deposit that offsets the fee. The issue here is that it's a non-existent deposit, which I'm not comfortable doing, especially as this is accounting. 2) Delete the transaction and replace it with manual ones. The issue here is that it's extra work for a fee calculation that should just work out the box. It would be nice if Koinly accounted for this correctly in the first place.

A number of records are missing entirely or there are duplicates.

uploaded new file still shows that i have doge even i dont have on my swissborg account,hone(hivemapper) shows 1000% roi which is not true,i am in loss with this one

When syncing a wallet, Koinly sometimes automatically marks legitimate transactions as spam, which produces an error where the reported balance doesn't match the calculated balance. When I remove the spam tag, I get mixed behavior. In many cases, the error remains on both the dashboard and wallet list view. Sometimes, the error goes away on the dashboard but remains in the wallet list view. In an article, Koinly mentions that ensuring calculated balance matches reported balance is a great way to make sure the accounting is right. But this makes it extremely difficult to distinguish legitimate errors from real ones, as sometimes the balance mismatches can be caused by a mix of wrong spam tags and missing transactions.

There seems to be an update in the kraken API for certain assets (from ticker to ticker.B). This is causing a mismatch between calculated and reported balance and also a difference in the portfolio total value

After the changes to transfer handling done in December, my portfolio never finishes the calculations - it just keeps "spinning". Restarting the calculations does not help Status Our dev team is investigating the cause and working on a fix