Bugs

Bug Report: Binance P2P Transactions Not Importing What is the issue? Binance P2P transactions are not being imported into CoinTracker via API, even though they appear in the exported file from Binance. Who is affected? Users who engage in Binance P2P trading and rely on CoinTracker to track their transactions automatically. What is the workaround? Currently, there is no supported method to import these transactions automatically. We recomend waiting for a fix from the team. If there is an urgent need to add these transactions the Binance CSV can be converted to CoinTracker format if it fails to upload. Keywords: Binance P2P, missing transactions, CoinTracker sync issue

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

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

Bug Report: Uphold Wallet Sync Missing Transactions What is the issue? Uphold wallets are not fully syncing via API, resulting in missing transactions and discrepancies between reported and calculated portfolio values. Who is affected? Users syncing their Uphold wallets through the API. What is the workaround? Users can request their raw Uphold CSV and manually import it into CoinTracker. Instructions for formatting and uploading are available in the Help Center . Keywords: Uphold wallet sync, missing transactions, XRP discrepancy, Uphold CSV import

Bug Report: Editing Asset in Transaction Doesn’t Persist What is the issue? When users attempt to edit a transaction and change the asset to an asset that shares the same name and ticker (e.g., selecting a different version of “Harold HAROLD”), the change appears to go through but does not persist after saving. The dropdown shows multiple identical-looking versions of the same asset (aside from the token image). Who is affected? Users editing transactions that involve assets with duplicate or misattributed names—specifically those where multiple assets share an identical name and ticker in the asset selector. What is the workaround? Currently, there is no reliable workaround. Users can attempt to re-edit the transaction, but changes often revert. You can upvote this post to stay updated on the fix. Keywords: transaction editing, asset not saving, asset dropdown bug, duplicate assets

Users may experience: Perpetual or prolonged wallet page loading state Unable to access wallet page in CoinTracker Error message: "Oops! This is unexpected. There was an error while trying to load your wallet. We're working to fix the problem. Check back later." Error message: "There was a problem while loading data, please refresh your page." Wallet page timing out resulting in 504 web page error Expected behavior: Users should not experience wallet page down time Pending further investigation, impacted user count is low. As a user, what should I do? Users can leverage the ' My Assets ' list on their dashboard to verify current wallet balances Users can also utilize their ' Balance difference ' tab on their tips page to reconcile any pending wallet balance differences Users can add wallets via their Dashboard using the ' Add-wallets ' button 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: add wallet, wallet, wallet page, 504 error

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: $PUMP Token Appears Legit Despite Being Flagged as Malicious What is the issue? The $PUMP token on Ethereum (Contract: 0xB6B15d694B07411823Fe04eCd27399f18C521574 ) is still shown as a legitimate asset in CoinTracker. Although $PUMP is still listed on CoinMarketCap (CMC) , it has been flagged as malicious (e.g., honeypot/rug pull) by our spam detection provider . However, since it maintains a valid CMC listing, it is not currently marked as SPAM in CoinTracker. This could lead to inflated or misleading portfolio values for users holding the asset. Who is affected? Any user who holds or has interacted with the $PUMP token on Ethereum. What is the workaround? There is currently no way for users to manually flag the token as SPAM. The CoinTracker team is reviewing the conflict between CMC status and third-party spam flagging. Keywords: PUMP token, flagged as malicious, CMC listed, Ethereum, spam detection, inflated portfolio

Bug Report: Inconsistent and Missing Edit Category Options on Mobile vs Web What is the issue? Users are experiencing inconsistencies and limitations when editing transaction categories across mobile and web platforms: The list of category options available when editing a transaction is different between mobile and web. For example, mobile may show ambiguous “Unknown” entries, while web displays categories like “Deposit” or “Margin Settle” – but these cannot be selected when editing. In some cases, the “Edit Category” option is missing entirely on the mobile app for transaction types where users expect it to be available (e.g., Trade transactions), even though the same transactions are editable on the web. Who is affected? Users who use both mobile and web platforms to manage their transactions and expect consistent editing capabilities. What is the workaround? There is no reliable workaround. Users may switch platforms or delete and recreate transactions to apply the correct category. Keywords: edit category missing, transaction category edit, mobile web inconsistency, platform parity, trade transaction edit

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