Product Feedback

Users may experience: Some users have reported their Tezos transactions related to staking rewards coming in as regular Receive transactions. This is causing an understated Income count. As a user, what should I do? No further action needed. 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. If there's an urgency to correct the transaction's category, users can update the transaction category following this guide . Thank you for your understanding and cooperation as we work to enhance your CoinTracker experience! Keyword: Tezos, staking rewards, wrong category, update staking, wrong income, income, receive transaction

Users may experience: Some users are seeing double inflows of tokens being swapped and an extra "Send" transaction, causing a capital gain that's much larger than it should be. The token balances stay correct; only the reported gain/loss on these specific transactions is affected. As a user, what should I do? No further action needed. 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. Keyword: Meteoria, Raydium, SOL swap, inflated capital gain, double inflow, Solana, wrong numbers

What is the issue? CoinTracker imports a Kraken USDC buy correctly but classifies the following hybridearnwithdrawal as a standalone send instead of an internal transfer into Kraken Earn. No corresponding receive is created and no Earn wallet is created. Who is affected? Users syncing Kraken accounts with Kraken Earn transactions involving hybridearnwithdrawal entries after a USDC purchase. What is the workaround? No workaround available. Affected users may upvote this post to stay notified of updates. Keywords: kraken, usdc, earn, withdrawal, ingestion

Users Feature Request: Auto classify Marinade Finance staking transactions to enhance user experience. Until this feature is implemented, users should manually categorize these transactions. Note: This would significantly improve accuracy and reduce manual effort for users interacting with Marinade Finance staking. As a user, what can I do? Until we can auto categorize these transactions, please manually categorize the stake transactions. You can upvote this feedback post to indicate you would like this feature added! Additional Information We have information on feature requests and what the status means in our help center . For further assistance or inquiries regarding this feature request you can contact the support team . Thank you for your feedback and cooperation as we work to enhance your CoinTracker experience! Keywords: Marinade Finance, staking, auto-classify, staking transactions, manual categorization

What is the issue? Some earlier WFLR reward transactions are visible on-chain as ERC-20 transfers and appear in the Bifrost wallet UI, but they do not appear in CoinTracker. Who is affected? Users importing the Flare address with earlier WFLR reward events that match this on-chain pattern may be affected. The issue also reproduces in a fresh account. What is the workaround? Users can manually create reward transactions to reflect their 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: wflr, flare, rewards, ingestion, csv exports

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