Bugs

Bug Report: Balance Differences What is the issue? Significant discrepancies between calculated and reported balances are appearing for certain crypto assets when Kraken is synced via API. This is occurring for both the Auto-Earn and Staking features in Kraken. Users that enable then disable these features may see balance differences in their wallets on CoinTracker. (see screenshots below) Who is affected? Users who enable/disable the Auto-Earn and Staking features in Kraken or unstake an entire asset from their Kraken Earn wallet. What is the workaround? There is currently not a workaround, however our Engineering team is aware of the issue and are working on a fix. How can users provide feedback? You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly. Keywords: balance differences, auto-sync issue, crypto assets, unstaked assets, Kraken

Users may experience: Users notice that there are several transactions missing upon initial import and during subsequent syncs that leave my balances incorrect and valuations inaccurate. It is not well understood what types of transactions or what features from Bitfinex, CoinTracker supports. Expected behavior: As a user who trades and manages my token portfolio on Bitfinex I expect CoinTracker to import all of my transaction history. As a user, what should I do? If you are missing certain types of transactions we would love to understand where we can improve our integration, please submit a new post here outlining the transaction type that is missing within CoinTracker from your Bitfinex exchange. Once you have created a new submission as instructed above, you can begin to reconcile your transaction history. Currently, users will need to manually add or edit any incorrect or missing transactions. Alternatively, if you are a user that is missing a lot of transactions we recommend that you transition your Bitfinex exchange to a CSV import instead of the our API integration. Users can format their Bitfinex transaction history CSV per this guide and import the CSV into CoinTracker as next step while we improve this integration. We recommend users stay vigilant when importing their Bitfinex exchange into CoinTracker. We recommend reviewing your transactions regularly for accuracy, users can manually create transactions should they be missing from your wallet. How can users provide feedback? You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: Bitfinex, missing transactions, balance differences, calculated balance

Users may experience: Some Binance accounts are failing to sync to CoinTracker No error message is displayed. Expected behavior: Binance accounts should sync seamlessly, with all transactions and balances updated correctly. As a user, what should I do? If Binance fails to sync, users can try uploading their history using their CSV according to our import instructions. Users can also upload their CSV as a generic CoinTracker CSV. You can do so by following the instructions in our support article: How to Convert your Transaction History to a CoinTracker CSV . Additional Information Please upvote this post to indicate that you are experiencing this behavior. We have information on bug reports and what the status means in our help center . For further assistance or inquiries regarding this bug you can contact the support team . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: Binance, sync issue, Binance not syncing

Users may experience: Terra (LUNA) and Terra Classic (LUNC) are recognized but missing price history, causing inflated or inaccurate unrealized gains. Notably, LUNA / LUNC appear to be causing a spike in users' portfolio balance around May 26, 2022. Expected behavior: Users expect full price history tracking for all supported tokens, including Terra (LUNA) and Terra Classic (LUNC), to accurately reflect unrealized gains and overall portfolio balance. As a user, what should I do? Users can either leave their LUNA / LUNC transactions as is or use a workaround by creating a custom currency for the partially supported token and replacing said token with the custom currency. Detailed instructions for creating a custom currency and editing transactions can be found here for creating a custom currency and here for replacing the token . All transactions with the partially supported token will need to be updated to the custom currency to ensure consistent token treatment. How can users provide feedback? You can upvote this forum post to indicate you are experiencing this behavior. The post status will be changed to Complete once a fix is rolled out to all users. Up-voters will be notified of the status change. I need additional assistance, who can I contact? For further assistance, please contact our support team directly . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: Terra, LUNA, Terra Classic, LUNC, price history, unrealized gains, custom currency

Users may experience: Incorrect display of the net amount of received assets in transactions where a fee is applied to both sides of the transaction. CoinTracker shows the gross amount instead of the net amount after the fee is deducted. Expected behavior: CoinTracker should accurately display the net amount of received assets after any applicable fees are deducted when fees are applied to both sent and received assets. As a user, what should I do? Users with fees on both the incoming and outgoing side of the transaction should deduct the amount of the fee from the receiving/incoming side of the transaction and ignore the second fee so there's no double fee on transfer. Additional Information Please upvote this post to indicate that you are experiencing this behavior. We have information on bug reports and what the status means in our help center . For further assistance or inquiries regarding this bug, you can contact the support team . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keywords: transaction display, fee deduction, net amount, trade record, Kraken

Bug Report: Inflated Gains Due to Small Sends in Multi-Call Transactions What is the issue? Some users are experiencing inflated capital gains when small transfers within multi-call transactions. Who is affected? Users who perform multi-call transactions across various blockchains, especially on ZkSync and Base, where small sends might be misclassified. What is the workaround? Users can ignore the transactions and instead create a separate send and receive - note that when the team addresses the issue, these manual edits could result in duplicate transactions. Keywords: multi-call transactions, inflated gains, small sends, incorrect capital gains, tax reporting