Bugs

What is the issue? Some Solana transactions that interact with DeFi protocols like Kamino Finance are categorized in a transaction labeled as "Multiple". In the "multiple" transactions are a group of individual transactions such as trades, add/remove liquidity, staking, etc. However, the order of operations may be miscalculated resulting in a negative balance. Example: "Multiple" transaction that contains a borrow and lending deposit may have the asset show the lending deposit first before the borrow. 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. Is there a workaround? As a workaround, users can ignore the "multiple" transactions that are affected by this issue and instead recreate the individual transactions manually. For the outflow (send) transaction, users can create it a second after the inflow (receive) transaction to ensure the order of operations is correct. Example: -"Multiple" transaction containing a borrow and lending deposit. -Recreate the Borrow (inflow) transaction first with the same date and time as the original "multiple transaction. -Recreate the Lending Deposit (outflow) transaction with the same date but the time being a second after the Borrow transaction. Note that when the team addresses the issue, these manual edits could result in duplicate transactions. 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

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

What is the issue? Solana rent fees (refundable), are causing discrepancies in DeFi transaction tracking such as Liquidity Pools, Minting, etc. The fees are being included in the wrong fields, such as in the Add Liquidity field. (see screenshot below) 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. Is there a workaround? As a workaround, users can manually recreate the DeFi transaction, but include the refundable (rent) fees as part of the Send portion instead of the Add Liqudity, Staking, etc. After the transaction is recreated, they can ignore the original transaction to avoid duplicates. Keep in mind that when the team addresses the issue, these manual edits could result in duplicate transactions. 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

What is the issue? The Robinhood API sync completes without error, but returns 0 balance and 0 transactions, even though the account has activity. What is the workaround? Users can manually import their Robinhood transaction history using a CSV. Instructions are available in the Help Center . Keywords: Robinhood API, zero balance, missing transactions, sync issue

Users may experience: Users may encounter "Needs review" transactions when unstaking liquid stake tokens (e.g., stSOL) in their wallets. This occurs because the unstaked stSOL transactions are not categorized correctly, while the received underlying SOL is categorized as Unstake. Note: Liquid staking means you can lock up your cryptocurrency (stake it) to earn rewards, but you also get a token that represents your staked amount. You can use this token like regular cryptocurrency, allowing you to trade or invest it while still earning rewards from the staking. Expected behavior: The unstaked stSOL transactions should be automatically categorized correctly, and the corresponding SOL received should not require additional manual adjustments. As a user, what should I do? To address this issue manually: Option 1: Change the categorization of the unstaked stSOL transaction to a normal receive (this will appear as a receive of SOL in CoinTracker at a later time than the send of stSOL). Option 2: Ignore the Unstake SOL transaction and manually apply the SOL information to the send of the stSOL, effectively creating a trade. A note on the manual edits: Option 1 will allow for the correct fair market value to be applied for the SOL at the time it was received from the unstaking operation. Option 2 will use the fair market value of the SOL at the time of the stSOL send. Please consult with a tax professional on which option best corresponds to your specific needs. 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: liquid stake, unstake, stSOL, SOL, categorization, needs review

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: 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: 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