Bugs

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

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

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

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: 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: Odd behavior with assets NFT on the user account. The transaction shows a value of the amount of the NFT without further details to identify the asset. (It does not always impact all transactions involving the same NFT) Expected behavior: The transaction should display the metadata (image and name) consistently for all supported assets. As a user, what should I do? Users impacted can utilize custom currencies to represent the impacted NFTs. Please ensure that all transactions with the same NFT utilize the same custom currency to avoid cost basis issues. 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: NFT, assets, transaction discrepancy