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: 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: Failure to sync new transactions from Uphold after previously authenticating successfully. User may see an error message: "We failed to sync your account. Please check your API keys and re-authenticate your account." Expected behavior: Users expect their Uphold accounts to sync successfully, importing all new transactions without errors. As a user, what should I do? -You may try reauthenticate your Uphold account by following the prompt on the Wallets page. If the issue persists, 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: Uphold, API sync failure, transactions not syncing, authentication error

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: 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: 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. As a user when I add or have added my Bitstamp exchange via the API integration on CoinTracker, I expect all of my transactions to be imported into 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? To reconcile these missing transactions and are identifying the missing transactions pro-actively, users can add those transactions manually, here is a support article on how to add transactions manually. If you believe that you are missing transactions but are not sure which transactions are missing, you can export your transaction history from your exchange via CSV, additionally, you can export your transaction history from CoinTracker for the same exchange ( support article ). Alternatively, users can import their transaction history instead. 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: Bitstamp, failed sync, missing transactions

Users may experience: A single asset (i.e. GALA) appearing twice in a wallet (Image 1) When filtering by one of the assets listed results in all transactions for both versions of the asset listed on the transactions page. CoinTracker does not track the older versions of forked assets, add your upvote here for improved tracking! It can be assumed that the older version of a token is no longer supported, in most cases the older version will appear as a blue logo asset and the newer version will be imported with the correct logo. In this case both the old and new version of the asset appear the same. Note: This is only affecting a few forked assets, most forked assets are not mapping to the same (newer) asset Expected behavior: Ability to differentiate between the two versions of a forked token and expect them to be distinguishable upon ingestion. The current token should inherit the appropriate price history and the older version of the token should appear as an unsupported token. CoinTracker recently made an update that matches tokens by token contract address. Some users report forked tokens still mapping to the current asset even when the contract addresses differ. CoinTracker has a know bug in which we do not maintain price pages for forked / archived tokens outlined here. As a user, what should I do? Users will need to update the mis-mapped version of the asset by manually creating a custom currency to represent to asset and replacing any transactions related to that asset with the custom currency. As an example, GALA v1 forked in May 2023 . CoinTracker currently uses the price history and mapping for GALA v2 and v1 tokens are being mapped to the current version. Users can update GALA txns prior to May 2023 with a custom currency to represent their GALA v1 assets. 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: fork, hard fork, GALA, coin-mapping

Users may experience: CoinTracker is not correctly recording the reward quantity included in a transfer transaction on Cardano. Instead of including the reward amount in the total value sent, it considers the rewards balance/quantity as a separate entity, causing discrepancies in send and receive amounts across wallets. Expected behavior: CoinTracker should correctly account for reward quantities in transfer transactions, treating the total amount sent (including rewards) as a single transaction, to avoid discrepancies and incorrect capital gains calculations. As a user, what should I do? Users will need to make manual modifications to correct this. Actions include: Importing ADA staking reward transactions via CSV to avoid balance issues. Editing transactions that are not transfer-matched to reflect accurate transfers. For transactions appearing as Send and Receive, ignore one (e.g., the Send) and update the Receive transaction to 'change type to transfer', specifying the outgoing side as the original Send wallet. This issue has been escalated to our engineering team for review, and we will update this post once a fix is deployed. 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: Cardano, ADA, rewards, transfer transaction, CoinTracker, capital gains, staking rewards

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