Below are the most common causes of Missing Cost Basis Warnings.
You didn't import the historical data from ALL of the exchanges or platforms that you bought, traded, earned, or transacted crypto on
You didn't include your data from ALL of the years that you have transacted with crypto
You have imported duplicate data (learn how to resolve this here)
You didn't include the crypto you received from mining, staking, interest earned, or other forms of income (Learn how here)
You interacted with a smart-contract or dApp that CoinLedger does not yet natively support and there are Uncategorized trades that need to be further classified (Learn how here)
You traded on both Coinbase and Coinbase Pro but did not upload both exchanges
You purchased or sold crypto directly from your self-custodied wallet provider but did not import those buys/sells (Learn more here)
You imported from a platform that supports buying crypto through third party sites like Banxa, MoonPay, Transak, or others. In these cases, Fiat purchases of crypto can look like plain deposits of crypto with missing cost basis. Learn more here.
You imported data from an exchange like Binance.US which has known data limitations. Learn more here.
Some exchanges like Binance.US only import one side of buys, which means you might have to edit a deposit to reflect your cost basis. Learn more here.
You bridged from one blockchain to another and need to merge two transactions within CoinLedger to show our app how you acquired an asset with a missing basis. Learn more here.
You need to merge together the potential bridge, transfer or trade transactions in your account that were not automatically mapped when you imported your data. Learn more here.
You can learn more about MCB Warnings here.
All of these above cases can be fixed by either importing or classifying your missing data.