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: Coinbase is failing to sync for some users. No error messages may be shown, but the account balance or transaction history is not synced or updated. Expected behavior: Users expect Coinbase to sync and reflect the correct balance and transaction history in their CoinTracker account. As a user, what should I do? There currently is not a workaround for this bug and it will need a fix from the team. We appreciate your patience while we work to resolve this. 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: Coinbase, sync, no transaction history, bug

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: 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: Continuous prompts to re-authenticate their Coinbase account Prompts are being received more frequently than what is expected, often on a daily or weekly basis. Expected behavior: Coinbase should successfully authenticate and remain synced to CoinTracker. As a user, what should I do? Users can follow the instructions prompted to re-authenticate their Coinbase exchange to re-establish the connection as needed until the issue is resolved. Alternatively, users can add their Coinbase transactions via CSV as a custom file here until the issue has been corrected. 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: Coinbase, re-authentication, re-authenticate, Coinbase exchange, reauth, error

Users may experience: Some wallets added through the Exodus integration are failing to pull either balances, transactions, or both. This is most commonly seen with Cardano Wallets with a known balance sync but with zero transactions The wallet does not sync at all. Note : Not all wallets on Exodus are supported by CoinTracker it is expected that these wallets not add to CoinTracker regardless if the wallet has a balance on Exodus. Expected behavior: It is expected that all supported blockchain addresses pull a complete transaction history into CoinTracker. As a user, what should I do? For a small number of missing transactions , users can manually input them into CoinTracker by following our guide: How to Manually Add a Transaction If the blockchain address is supported , consider removing the Exodus integration and directly adding the blockchain address instead. Here’s how: How to add wallets and exchanges to CoinTracker . For unsupported chains , users can import the transactions using a CSV file. Detailed instructions are available here: Importing Transaction Histories to CoinTracker Using CSVs . 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: Exodus, wallets, balances, sync

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: 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? If you encounter this issue, we currently do not support the direct editing of timestamps for API synced transactions. To correct any balance errors, manually recreate the transaction with the timestamp that aligns accurately with your transaction history. View our guide for manually creating a transaction . 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

Users may experience: LUNC transactions transactions and wallet holdings on CoinSpot and Gemini are showing LUNA instead of LUNC. The price for LUNC is much lower than the price that is reflected for LUNA. This means that affected users will see inflated values on their transactions and capital gains that are too high on the tax center and forms. The dashboard and portfolio will also show an excessively high value for the quantity of the token that the user holds. Expected behavior: CoinTracker should map to the correct LUNC and LUNA assets for exchanges. As a user, what should I do? The workaround is to edit transactions to reflect LUNC. This will correct the pricing on transactions and tax calculations. 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: LUNC, LUNA, coin mapping, balance differences

Users may experience: Users are reporting failed syncs when importing their Bitstamp exchange. These failed syncs result in new transactions missing and in some cases no transaction history imported at all. Users may see the below state when reviewing their Bitstamp exchange in CoinTracker. Users are reporting missing transactions upon sync and ongoing syncs, the behavior is not consistent with a specific currency. The behavior appears to be a result of the type of buy transaction within Bitstamp. Some examples include: Instant, Market and normal buys. Expected behavior: CoinTracker should be importing all transactions from Bitstamp exchange. As a user, what should I do? If your Bitstamp exchange is failing to sync to CoinTracker you can upload the transaction history via CSV by following this guide . Note: If your account partially synced, remove the partial sync to avoid duplicate transactions when uploading the CSV. Keywords: Bitstamp, failed sync, missing transactions