Bug reports (public)

BTC: after 11th january, Kraken changed ticker from "BTC.M" to BTC and type from "staking" to earn". any BTC Earn transaction after 11th january gets skipped by Koinly. MATIC: any MATIC earn transaction after 12th march gets skipped by Koinly.

After the migration of assets on Kraken and the update to the ticker from ticker.S to just the ticker. The rewards for the assets are no longer imported using the Kraken API.

If I had multiple trades during the day that triggered same-day pool, my dashboard graph may show an implausible spike, double-counting the volume of the trades (adding both to cost basis and value) Note While this affects the plausibility of the graph, it has no effect on the crypto calculations and does not affect reports, balances on the reports, etc.

after fixing Osmosis API 3 days ago, my wallet now gets the "Something went wrong while syncing, try again in a few minutes or contact support." error. tried at different times on multiple days, no luck.

The IOTA API seems to be broken. No transactions are updated with the new Firefly wallet. See here: https://discuss.koinly.io/t/iota-wallet-does-not-show-transactions/8371

ETH staking rewards on Kucoin (ETH2, KPOL) only appear in the "Account History_Funding Account" csv file, but Koinly is skipping the file. (KPOL rewards have been sunset on 14th August 2023, so from there onwards only ETH2 rewards)

When checking CSV import summary for errors, the row indicated is incorrect - it's offset by 2 (ignores header row and starts the count from 0). Since it's called "row", it should start the count from 2 and match the line number in the CSV file. It could also be renamed to "transaction" and start from 1.

I've noticed in more than one account (I have multiple Koinly accounts) that something seems to be wrong with the USDC transaction fees calculation in the Coinbase integration. All cases I noticed were related to recently added transactions that were added using the Coinbase API (maybe they changed the data structure that comes through their API?). The calculation seems to be wrong and "Missing purchase history" errors of small USDC values start to pop up. So far, I've only experienced this issue on transactions involving USDC.

Any operation performed on a starknet wallet is marked as deposit even when it's clearly a cost or a swap.

CA: 0xC71B5F631354BE6853eFe9C3Ab6b9590F8302e81