Describe the problem:
When I import using the Kraken API, I get the “balances do not match” for 11 of the imported cryptos. When I drilled down on one of them, it turned out that for a particular transaction (TD7R3A-CKECL-6L3ABX) it had recorded the “received” value twice: once specifying the parent order id (ovjk7g-nbrxn-vn5wox) as the Transaction hash and once referencing the relevant ledger id (lzec67-lfwyp-i5ilja) as the Transaction Hash. This happens with many transactions, resulting in the mismatch between the stated balance provided by the API and the calculated balance based on order and ledger entries from the API. It appears to be a (very serious) bug.
Which exchange/wallet is this regarding?
Kraken
How did you import data into this wallet?
API
What have you tried to fix this so far?
If I import via the CSV mechanism, all the coin balances match those as shown by the API mechanism, but without the duplicate entries. So this seems to be a viable workaround.
However, it took me a full day of analysis to come to this conclusion. It would be nice to have a bug fix for this and, in the meantime, to mark “CSV” as the recommended import approach.