Bugs

Bug Report: Manual Transfers Double-Count Fee if Net Sent Amount is Used What is the issue? When users upload manual transfers via CSV and subtract the fee from the sent amount (i.e., use a net value), CoinTracker still deducts the fee separately from the sending wallet. This causes the wallet to be debited for both the already-reduced send amount and the separate fee, effectively double-counting the fee. Who is affected? Users manually creating transfer transactions, especially via CSV, where they net the fee from the send amount and also include the fee as a separate line item. What is the workaround? Users should either: Use the gross sent amount (equal to the received amount + fee), or Omit the separate fee row if the sent amount already includes the fee. A best practice is: > Sent = Received , and the fee is handled as a separate outflow. Keywords: transfer fee bug, CSV import, manual transactions, double-counted fee, wallet outflow issue

Bug Report: BTC Wallet Fails to Sync (504 Error) What is the issue? When attempting to add a Bitcoin wallet using an xPub/yPub/zPub key, users may encounter an error: "Response not successful: Received status code 504." This prevents the wallet from syncing. Who is affected? Users adding Bitcoin wallets via xPub/yPub/zPub keys. What is the workaround? If syncing via xPub/zPub fails, users can manually import their BTC transactions using a CoinTracker-compatible CSV. Instructions are available in our support article: How to Convert Your Transaction History into CoinTracker-Compatible CSV Format . Please upvote this post if you are experiencing this issue so we can prioritize investigation. Keywords: Bitcoin, xPub sync, 504 error, BTC wallet not syncing, manual CSV import

What is the issue? Multiple incorrect MATIC to POL trades are appearing for Binance US users. These entries are the result of a token swap that happened earlier this year. Who is affected? Binance US users who held or interacted with MATIC during the token swap process. What is the workaround? No action is needed at this time. The issue is being investigated by our engineering team and will be resolved automatically. Keywords: MATIC to POL, Binance US, token swap, incorrect trades

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

Bug Report: SOL Wallet Syncing Shows Balance Discrepancies What is the issue? Users are reporting a mismatch between their calculated SOL balance and the value reported for the SOL address. Who is affected? Potentially any user with a SOL address added. If you are impacted you will see an unexplainable balance difference in SOL. What is the workaround? There is currently no automated workaround. Users can manually review their transaction history or import missing data via CSV if they identify gaps. Keywords: SOL wallet sync, SOL balance mismatch, Solana discrepancy, reported vs calculated balance, missing SOL transactions

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: 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: 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

What is the issue? The ordinal provider previously used has shut down, which prevents rune and ordinal activity from appearing in recent BTC transactions. Historical data should remain intact but new ordinal transactions will only include the BTC involved. Note: Provider has shut down mid-May 2025. Who is affected? Users with BTC wallets that have rune or ordinal transactions after mid-May 2025. What is the workaround? We're currently working on setting up our new provider for ordinals. In the meantime, users can manually edit their transactions to include their ordinal tokens or wait until replacement provider is integrated. Keywords: BTC wallet, ordinal provider shutdown, rune missing, Bitcoin ordinals, transaction sync issue

Bug Report: eToro Transaction Report Upload Fails What is the issue? Users attempting to upload their eToro transaction reports encounter an error: "Failed to find all required column headers in eToro transaction report column headers." Who is affected? Any users trying to upload their eToro transaction reports. What is the workaround? Users can manually convert their eToro .xlsx report to a CoinTracker-compatible CSV before uploading: Follow the instructions in this guide to convert your file. Upload the newly formatted CSV file to CoinTracker. Keywords: eToro upload error, transaction report, column headers issue, CoinTracker CSV conversion