Bugs

Users may experience: When attempting to upload a transaction history to CoinTracker from the Binance File Import page , the upload fails. User will see the following error: Incomplete transaction data. Required fields (fee, buy, sell) are missing or not properly formatted. Expected behavior: Users should be able to successfully upload transaction histories via the native CSV formats from Binance via the File Import page. Note: Some transaction Operations are not supported and may be ignored upon import. Add an upvote to this feature request: Support the native CSV format when importing Binance exchange for future updates. As a user, what should I do? Users can continue to upload their Binance files by converting the files to our CoinTracker CSV format . 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: upload failure, Binance, CSV, file import

Bug Report: SPAM Asset "MAGA" Inflating User Portfolios What is the issue? Users are reporting that a SPAM asset, "MAGA," is inflating their portfolio balances. Although the asset is flagged as SPAM by our provider, it is not appearing as SPAM in CoinTracker, and users are unable to mark it as SPAM. Who is affected? Users who were airdropped the SPAM asset MAGA in their portfolios on Base Chain . What is the workaround? Currently, there is no user-side fix. Users cannot manually exclude or mark the asset as SPAM. Engineering intervention is required to ensure SPAM flagging works correctly and to backfill data due to a known outage. Keywords: SPAM asset, inflated portfolio, MAGA token

Users may experience: Only the send portion of the transfer is picked up and not the receive Wallet balance differences pertaining to the asset sent to the other portfolio Note: This is only for transfers between portfolios within the standard Coinbase platform (including Advanced) Expected behavior: Transfers between portfolios should appear as an transfer between internal Coinbase wallets on CoinTracker. 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, Coinbase Advanced, Transfer, Portfolio

Users may experience: Kraken ETH/ETH2 staking transactions are showing as a send and receive transaction and not pairing as a trade as would be expected. Expected behavior: Transactions should correctly pair trade transaction. Ideally these transactions should show as a stake and unstake when ETH is traded for ETH2 or vice versa. As a user, what should I do? To correct this, you can create a manual transaction to accurately represent the trade and then categorize it as either a stake or unstake. For guidance on how to manually add a transaction, please refer to this guide on manually adding a transaction . To change the category of a transaction, please visit this guide on changing a transaction category . 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: Kraken, ETH, ETH2, staking, transactions, manual transaction, categorize

Users may experience: Some Solend transactions are incorrectly including cSOL on the "Sent" and "Received" sides of the transactions Some Solend transactions are incorrectly imported Expected behavior: The transaction should match cSOL balances changes as seen on solscan. As a user, what should I do? For better handling the transaction can be split into multiple parts to ensure the correct cost basis and taxation are applied. 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: solend, cSOL, solana incorrect