Product Feedback

What is the issue? Crypto.com App CSV files are being imported incorrectly, which causes inaccurate transaction histories and leads to incorrect balances in user portfolios. Some balance discrepancies may appear in the account. These discrepancies are related to staking activity on Crypto.com , as staked assets are not included in the total wallet and portfolio balances. Who is affected? Users who import their transaction history using the Crypto.com App CSV file and have staking transactions in their transaction history. What is the workaround? There is currently no workaround. Users are encouraged to upvote this post for updates as the issue is investigated. Keywords: Crypto.com CSV import, negative balances, incorrect import, Crypto.com app bug

Users Feature Request: Integrate XDC Wallet, a client-side interface for interacting with the XinFin blockchain. Learn more about XDC Wallet here . As a user, what can I do? Until this feature is supported, you can add your transaction history via CSV by downloading the CSV export of your transactions, re-formatting it into the CoinTracker CSV format , and importing this file here . For more details, you can follow this guide . You can 🔼 upvote this feedback post to indicate you would like this feature added! The post status will be changed to Complete should we pursue this feature. 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 feedback and cooperation as we work to enhance your CoinTracker experience! Keywords: XDC, XinFin, integration, wallet, add wallet

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

Users may experience: CoinTracker is not correctly recording the amount that is not spent in a "send" transaction on UTXO blockchains such as Bitcoin and Cardano. Instead of showing the returned amount as a transfer, it is recorded as a receive and the crypto receives a new cost basis as if it were just purchased. Expected behavior: The expected CoinTracker behavior would be to create a send transaction for the spent amount (triggering a taxable event) and a transfer transaction for the unspent amount that was returned, retaining its original cost basis and age for gains calculations. As a user, what should I do? If you wish to make manual modifications to correct this, you'll enter two transactions and add the correct tags for send and transfer: A send transaction for the original amount. A transfer transaction for the unspent amount that is received back to your wallet address. Alternatively, users can add xPub/yPub/zPub or Stake Keys instead of individual addresses to mitigate the behavior. 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: UTXO, send transaction, transfer transaction, capital gains, CoinTracker, ADA, BTC

Users may experience: As a user, when I import the blockchain.com ZIP to CoinTracker I expect all of the transactions within the CSV to be imported correctly. Users report Send transactions are incorrectly double counting fees on the outgoing asset and the fee column. As a user, what should I do? As a workaround, users can manually edit the outgoing amount to reflect the correct outgoing amount without the fee. 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: ZIP, imported wallet, blockchain.com , blockchain.com fees, fees incorrect, double fees