Bugs

What is the issue? Some Solana transactions that interact with DeFi protocols like Kamino Finance are causing cost basis loss. This is due to the order of operations of a "multiple" transaction causing negative balances. 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. 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

What is the issue? Solana rent fees (refundable), are causing discrepancies in DeFi transaction tracking such as Liquidity Pools, Minting, etc. 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. 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 rent fees, DeFi transactions, refundable fees, Solana transaction errors

Users may experience: Users report some transfer transactions are not transfer matching on the Solana blockchain. Users will see a separate Send and Receive transaction representing the two sides of the transfer (Image 1) Note: The Send transaction will contain a small SOL entry, representing a fee. Expected behavior: While the Transfer transaction is the intended activity, CoinTracker currently transfer matches 1:1 transactions meaning that the Send side of the transaction needs to match the Receive side of the transaction. In this case, there is a small SOL entry that represents a non-gas, causing the transfer match to fail The small SOL entry is expected as per the blockchain, there are non-gas fees in various SOL transactions. As a user, what should I do? For now, users will need to manually update their SOL transactions to properly reflect the transfers. 1️⃣ Manually ignore the non-gas fee entry send of SOL—this will allow the transfer to autodetect correctly. 2️⃣ Recreate the non-gas fee entry send of SOL as a manual transaction, ensuring it is recorded as a single-entry Send transaction. In the example below, once the non-gas fee entry send of SOL is ignored, the CHONKY transfer should correctly autodetect with CHONKY appearing on both the Send and Receive side of the transaction. The only manual action needed beyond ignoring the sent SOL asset is creating a separate single-entry Send transaction for the non-gas fee entry of SOL. This ensures the transfer is properly matched while accurately representing the fee. 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: transfer, SOL, solana, transfer match, fee

Users may experience: As a user, when I import the blockchain.com ZIP to CoinTracker I expect all of the transactions within the CSV to be imported correctly. Users report Send transactions are incorrectly double counting fees on the outgoing asset and the fee column. As a user, what should I do? As a workaround, users can manually edit the outgoing amount to reflect the correct outgoing amount without the fee. 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: ZIP, imported wallet, blockchain.com , blockchain.com fees, fees incorrect, double fees

Users may experience: Users are reporting failed syncs when importing their Bitstamp exchange. These failed syncs result in new transactions missing and in some cases no transaction history imported at all. Users may see the below state when reviewing their Bitstamp exchange in CoinTracker. Users are reporting missing transactions upon sync and ongoing syncs, the behavior is not consistent with a specific currency. The behavior appears to be a result of the type of buy transaction within Bitstamp. Some examples include: Instant, Market and normal buys. Expected behavior: CoinTracker should be importing all transactions from Bitstamp exchange. As a user, what should I do? If your Bitstamp exchange is failing to sync to CoinTracker you can upload the transaction history via CSV by following this guide . Note: If your account partially synced, remove the partial sync to avoid duplicate transactions when uploading the CSV. Keywords: Bitstamp, failed sync, missing transactions

Users may experience: Balance differences flagged on their XRP wallet page balances Missing transactions within their XRP wallet, non-native tokens not imported (i.e. CORE, SOLO, etc.) Reported balance is displayed accurately but calculated balance is incorrect due to missing transaction history resulting in incorrect calculations On the XRP block explorer missing transactions will appear as OFFER transactions (Image 1) *Note: See our balance difference article for more information. * Expected behavior: CoinTracker should be importing full transaction history, this includes Trade transactions for XRP wallet. Proper trade transaction import will prevent balance difference discrepancies. As a user, what should I do? Users will need to add missing transactions manually . Upvote this feature request ! We want to improve our XRP integration, add an upvote to be notified should we pursue an improved XRP blockchain support! 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: XRP, CORE, SOLO, Coreum, Sologenic, trades, missing transactions, balance differences

Users may experience: Users may be missing XLM transactions when syncing their Stellar Wallet. As a user, what can I do? Users can add their transaction history via CSV by first downloading the CSV export of your transactions, re-formating it into the CoinTracker CSV format , and importing this file as a generic CSV . Alternatively, users can manually add missing transactions individually. 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! Keyword: Stellar, XLM, missing transactions, balance difference

Users may experience: Odd behavior with assets NFT on the user account. The transaction shows a value of the amount of the NFT without further details to identify the asset. (It does not always impact all transactions involving the same NFT) Expected behavior: The transaction should display the metadata (image and name) consistently for all supported assets. As a user, what should I do? Users impacted can utilize custom currencies to represent the impacted NFTs. Please ensure that all transactions with the same NFT utilize the same custom currency to avoid cost basis issues. 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: NFT, assets, transaction discrepancy

Users may experience: Fees are not being imported correctly (including when using the re-import feature) on Nicehash wallets. Expected behavior: All mining rewards and fees should be imported correctly. 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. Users can import the fees if needed as a CSV to represent these missed transactions. 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 . Keywords: Nicehash, API sync, fees, historical data

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