Product Feedback

What is the issue? Some users have reported that their staking balance for Binance US is no longer appearing on CoinTracker after performing a sync. Binance US staking transactions are still being picked up, but the reported staked balance appears to be missing. Who is affected? Users who have connected their Binance US accounts via API and partake in staking. 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. Keywords: Binance US staking missing, Binance staking sync issue, Binance US stake problem, missing staked balance, Binance staked

Bug Report: What is the issue? Transactions from KyberSwap Aggregator Executor V3 are ingested and decomposed into multiple trade legs that result in inconsistent cost basis display on sale transactions, despite correct underlying cost basis tracking. Who is affected? Users with transactions executed through KyberSwap Aggregator Executor V3 involving partial asset returns and multiple outputs. What is the workaround? Users can manually edit or recreate the transaction. For example, if a transaction sends a large amount of an asset, receives a slightly smaller amount of the same asset back, and also receives another asset, the transaction can be recreated to reflect the net amount disposed rather than the full amount sent plus the amount received back. Keywords: kyberswap, ingestion, transaction decomposition, cost basis

What is the issue? Jupiter DCA Fill order transactions are recorded with $0 capital gain on some trades. Who is affected? Users with Jupiter DCA Fill orders. What is the workaround? Users can edit the proceeds of the Trades to reflect the correct capital gain. 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: dca, trades, capital gain, jupiter, transactions

What is the issue? Jupiter Limit CanceledOrder and DCA CloseOrder proceeds are distributed evenly between the returned asset and the returned SOL rent deposit. This records the returned SOL with an inflated cost basis, and subsequent inflated capital gain upon disposal of that SOL. Who is affected? Users with canceled Jupiter Limit orders and closed Jupiter DCA orders. What is the workaround? Users can ignore the returned SOL in the Close Order where the cost basis is inflated. 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: sol, cost basis, jupiter, dca, limit orders

What is being requested? Support ETH staking flows where the deposit address and withdrawal address are different wallets. The system should correctly track staking and unstaking transactions when funds are withdrawn to a different address than the original staking source. Why is this needed? Current handling works when staking and withdrawal occur within the same wallet. When different wallets are used, unstake transactions are flagged for review. What can users do now? You can upvote this forum post to indicate you would like this feature added. Up-voters will be notified of the status change. Keywords: eth staking, withdrawal address, multi wallet, unstake flow, transaction tracking

Currently, long and short trades show as send/receive transactions. Would like native support at least on Arbitrum for GMX. Would rather not pay Cointracker for me to do CSV field matching

Bug Report: Coinbase Loans Incorrectly Categorized What is the issue? Some Coinbase loan transactions are being incorrectly categorized as Sends instead of Lending Deposits . Who is affected? Users with Coinbase lending or loan transactions . What is the workaround? At this time, users can manually edit the affected transactions and reclassify them as lending-related activity until this issue is resolved. Keywords: Coinbase loans, lending deposits, incorrect categorization, Coinbase sync issue

Bitcoin OS ($BOS) shows as 1,367,351,000,000 on cointracker where it should be 13,673.51 This is from my cardano wallets

Feature Request: Add Caleb & Brown to Supported Wallets in CoinTracker What is being requested? The ability to integrate Caleb & Brown as a supported wallet in CoinTracker, similar to other platforms. This would allow users to seamlessly sync their transactions, deposits, and withdrawals directly from Caleb & Brown to CoinTracker. Why is this needed? Caleb & Brown is a well-known brokerage service for cryptocurrency trading and investments. Currently, users cannot connect their Caleb & Brown accounts to CoinTracker, requiring manual import of transactions. Adding this support would: Enable automatic synchronization of transactions. Enhance portfolio tracking and accuracy. Streamline tax reporting by consolidating data automatically. What can users do now? At present, users must manually import transaction data from Caleb & Brown using CSV files. Keywords: Caleb & Brown, wallet integration, CoinTracker, brokerage, portfolio management

What is the issue? Transactions are not syncing via the Huobi Global exchange integration for some users. Who is affected? Users with a Huobi Global exchange integration may be affected. What is the workaround? Affected users may follow the steps below to import their Huobi transaction history CSV in the meantime: Export transactions file from HTX Re-format it using our CoinTracker CSV template and guide CoinTracker CSV article Keywords: huobi, exchange integration, transaction sync, missing transactions