Product Feedback

Users Feature Request: Add the ability for users to edit and change transaction categories for multiple-operation transactions. As a user, what can I do? Users can ignore the transaction and manually create a new transaction, allowing you to edit the category. You can upvote this feedback post to indicate you would like this feature added! The post status will be changed to Complete should we pursue this feature. 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 feedback and cooperation as we work to enhance your CoinTracker experience! Keywords: edit, multiple, multiple-operations, category

What is the issue? Some Receive Transactions are being hidden from the Transaction page. Transactions with a generic onchain operation of RECEIVE and those manually entered as RECEIVES are being automatically hidden. Who is affected? Users looking for RECEIVE transactions on the Transaction page may not be able to find transactions as they are hidden. What is the workaround? Currently there is no way to unhide these transactions. Please upvote this feedback item if you are experiencing this issue. Keywords: transactions, receive, filters, hide_dust, visibility

What is the issue? Users cannot manually change the category of a token migration from Trade to Asset Migration. The update returns the error message: "There was an error while trying to update one operation." Who is affected? Users attempting to change the category of a token migration (i.e. MATIC to POL) from Trade to Asset Migration. What is the workaround? No workaround available. Users may upvote this post to remain notified of updates. Keywords: matic, pol, category, migration, operations

What is the issue? Base chain trades using Uniswap V4 are imported as “Multiple” transactions instead of a single trade. The outflow is imported as Send and the inflow is imported as Collect Rewards. Who is affected? Users importing Base chain Uniswap V4 trades from crypto to ETH. What is the workaround? No workaround available. Users may upvote this post to remain notified of updates. Keywords: base, uniswap v4, trade import, eth, transaction classification

What is the issue? Non-US users may see USD sync to their Kraken account when using the automatic sync feature and custom CSV import option. As a user, what can I do? You can 🔼 upvote this feedback post to indicate you would like this feature added! The post status will be changed to Complete should we pursue this feature. Up-voters will be notified of the status change. For further assistance, please contact our support team directly . Thank you for your feedback and cooperation as we work to enhance your CoinTracker experience!

Bug Report: Kraken Wallet Fee Misattribution Causing Balance Discrepancies What is the issue? Kraken balances are showing substantial discrepancies due to fee misattribution. For example, BTC transaction fees are being attributed to a different wallet (“other transactions”) instead of the Kraken BTC wallet. Users may find transactions in their "Other transactions" wallet that were automatically added due to the synced fees. Who is affected? Potentially, any users who sync Kraken via API. What is the workaround? Users should await a fix if possible - otherwise, ignore the fee from the synced transaction and add a new transaction to represent the fee from the correct wallet. Keywords: Kraken balance incorrect, BTC fee attribution, wallet misattribution, transaction fee issue, Kraken sync problem

What is the issue? Helium Voter Stake Registry transactions may be tracked as Trades instead of a Stakes. Who is affected? Users with Helium Voter Stake Registry staking transactions that include position initialization and deposit instructions may see this classification. What is the workaround? Users may manually edit the transaction category to Stake to reflect on-chain activity. ⚠️ Manual Edit Disclaimer Manual edits are a temporary workaround and will not be overwritten by future fixes or re-syncs. However, manual changes can sometimes result in duplicate transactions or other unintended side effects. For this reason, edits should be made with caution. Once a permanent fix is released, manually edited transactions may need to be reviewed or removed to ensure accuracy. Keywords: helium, stake, trade classification, hnt, solana

Bug Report: MATIC to POL Migration Classified as Taxable Trade What is the issue? Token migrations from MATIC to POL (Polygon Ecosystem Token) are being classified as taxable trades instead of non-taxable migrations. This results in incorrect unrealized returns and cost basis calculations. Who is affected? Users who held MATIC on Coinbase or Binance US during the automatic MATIC to POL migration period. What is the workaround? Users can manually reclassify the affected transaction by selecting the ⋮ menu on the transaction and choosing "Mark as non-taxable." ⚠️ Manual Edit Disclaimer Manual edits are a temporary workaround and will not be overwritten by future fixes or re-syncs. However, manual changes can sometimes result in duplicate transactions or other unintended side effects. Edits should be made with caution. Once a permanent fix is released, manually edited transactions may need to be reviewed or removed to ensure accuracy. Keywords: MATIC POL migration, token swap, taxable trade, cost basis, Coinbase Binance US

Users Feature Request: As a user, I would like to see the cost basis of assets when I transfer them between my wallets/exchanges. The cost basis carries through these transfers, but it is not clear that this is happening. As a user, what can I do? You can upvote this feedback post to indicate you would like this feature added! The post status will be changed to Complete should we pursue this feature. 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 feedback and cooperation as we work to enhance your CoinTracker experience! *Keywords: cost basis, transfers, transactions page,

What is the issue? When a Uniswap V3 NFT is transferred, the associated virtual LP tokens do not transfer with it. This creates a balance difference when liquidity is later removed from the recipient wallet. Who is affected? Users who transfer a Uniswap V3 NFT to another wallet and then remove liquidity using the recipient wallet. What is the workaround? No workaround available. Users may upvote this post to remain notified of updates. Keywords: uniswap v3, nft transfer, virtual lp, liquidity removal