Bugs

Users may experience: Some users will see the following error when adding their Cosmos wallet: We could not add your wallet as this address is invalid. Please follow the instructions below and try again or An error has occurred, please try again. Some users will be able to successfully add their Cosmos wallet but only sync partial transaction history missing their oldest transactions Users that previously successfully added their Cosmos wallets may no longer sync Expected behavior: Cosmos wallets should add successfully when added to add wallets page Syncs should occur daily was added to CoinTracker All supported transaction history should be imported into CoinTracker As a user, what should I do? If you are in a hurry we recommend exporting your COSMOS transactions as a CSV and importing them into CoinTracker using this guide. . We apologize for the inconvenience! 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! Keyword: Cosmos, ATOM, sync failure, sync, missing transactions

Users may experience: Users report that the cost basis per coin value is not accurate When calculating the average cost basis via the transactions CSV the value calculated does not match the value displayed on the performance page Expected behavior: Users expect to see consistent values across CoinTracker, if users see the average cost per coin on their performance page, they should have full confidence that the value is accurate and matches their transaction history. As a user, what should I do? If a user sees inflated or deflated cost basis values, we recommend first verifying if and transactions for their asset have a cost basis of zero, alternatively they may want to check if there cost basis is abnormally high within the transactions page. Users can also hang tight! Our team is investigating this 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! Keyword: performance, cost basis, cost basis per coin, wrong numbers

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: Transfer transactions synced with a variance in timestamps leading to insufficient quantity errors. - This occurs when one part of a transfer transaction is synced with an earlier timestamp than its counterpart, causing discrepancies in the sequence of transactions and resulting in balance errors. Expected behavior: Transfer transactions sync with accurate timestamps that maintain the correct sequence of transactions and ensure balance calculations are error-free. As a user, what should I do? To correct any balance errors users can adjust the datetime slightly (e.g., by a minute) by using the "Edit Date" option on a transaction. This should resolve the callout. 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: transfer transactions, timestamp variance, insufficient quantity errors, balance discrepancies

What is the issue? The Tax Loss Harvesting (TLH) page may display assets that users no longer hold in their wallets. This issue can also occur on the Tax Lots page, causing confusion about which assets are currently owned. Note : Stale data or wallets with inaccurate reported balances can also cause this behavior. If you are experiencing this, please first check that your ending balance for the asset aligns with your expectations. Who is affected? Users reviewing their tax lots and tax loss harvesting opportunities may see incorrect asset listings. What is the workaround? There is currently no workaround for this bug. The team is aware of the issue and working on a resolution. We appreciate your patience. This issue was reported December 2024. Keywords: tax loss harvesting, tax lots, missing assets, incorrect holdings

Bug Report: Unable to update tax date on mobile or web What is the issue? Users are unable to update their tax year through the mobile app or web platform. Who is affected? All users are unable to make a change to the tax start date. What is the workaround? Users can temporarily resolve this issue by switching their home country, which adjusts the tax date to align with the countries default setting. Note: this workaround still does not allow users to choose a custom date Keywords: tax year update, mobile issue, web 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

What is the issue? Users with more than 1000 transactions are encountering the error 99999-OFX-UNSUCCESSFUL when attempting to import their CoinTracker data into H&R Block. Who is affected? Users with more than 1,000 transactions importing their data to H&R Block Online. What is the workaround? This is a transaction limitation on H&R Block's side, and we are working with them to increase the limit. In the meantime, users can follow the steps in our help article to enter their crypto tax data in H&R Block. Keywords: H&R Block import error, CoinTracker tax data, 99999-OFX-UNSUCCESSFUL, OFX error

Users may experience: Users report some transfer transactions are not transfer matching on the Solana blockchain. Users will see a separate Send and Receive transaction representing the two sides of the transfer (Image 1) Note: The Send transaction will contain a small SOL entry, representing a fee. Expected behavior: While the Transfer transaction is the intended activity, CoinTracker currently transfer matches 1:1 transactions meaning that the Send side of the transaction needs to match the Receive side of the transaction. In this case, there is a small SOL entry that represents a non-gas, causing the transfer match to fail The small SOL entry is expected as per the blockchain, there are non-gas fees in various SOL transactions. As a user, what should I do? For now, users will need to manually update their SOL transactions to properly reflect the transfers. 1️⃣ Manually ignore the non-gas fee entry send of SOL—this will allow the transfer to autodetect correctly. 2️⃣ Recreate the non-gas fee entry send of SOL as a manual transaction, ensuring it is recorded as a single-entry Send transaction. In the example below, once the non-gas fee entry send of SOL is ignored, the CHONKY transfer should correctly autodetect with CHONKY appearing on both the Send and Receive side of the transaction. The only manual action needed beyond ignoring the sent SOL asset is creating a separate single-entry Send transaction for the non-gas fee entry of SOL. This ensures the transfer is properly matched while accurately representing 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! Keyword: transfer, SOL, solana, transfer match, fee

What is the issue? Some Solana transactions that interact with DeFi protocols like Kamino Finance are categorized in a transaction labeled as "Multiple". In the "multiple" transactions are a group of individual transactions such as trades, add/remove liquidity, staking, etc. However, the order of operations may be miscalculated resulting in a negative balance. Example: "Multiple" transaction that contains a borrow and lending deposit may have the asset show the lending deposit first before the borrow. As a user, what should I do? 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. Is there a workaround? As a workaround, users can ignore the "multiple" transactions that are affected by this issue and instead recreate the individual transactions manually. For the outflow (send) transaction, users can create it a second after the inflow (receive) transaction to ensure the order of operations is correct. Example: -"Multiple" transaction containing a borrow and lending deposit. -Recreate the Borrow (inflow) transaction first with the same date and time as the original "multiple transaction. -Recreate the Lending Deposit (outflow) transaction with the same date but the time being a second after the Borrow transaction. Note that when the team addresses the issue, these manual edits could result in duplicate transactions. 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: Solana DeFi, review suggested error, transaction classification, swap issue, liquidity pool, borrow, lending