Beware of phishing attacks, Ledger will never ask for the 24 words of your recovery phrase. Never share them. Learn more

Solving bad-txns-missingorspent error

This article explains how to solve the bad-txns-missingorspent error that you may face in Ledger Live when sending Bitcoin (BTC)  to another address.


One of the reasons why this error can appear in Ledger Live is when you are trying to send an already spent UTXO output in the failed transaction. It can happen due to an occasional error in the synchronization of your BTC account with blockchain explorer or after the update of Ledger Live.

Our engineering team is currently investigating why this is happening and we will update you as soon as possible if there is a fix.


A solution to this problem will be to force the account to synchronize with a blockchain explorer.

  1. Make sure everything is up to date (Ledger Live, firmware, BTC app)
  2. Clear cache in Ledger Live and try to send the transaction. You can find detailed instructions here.
  3. (optional) If clearing the cache did not solve the problem, try to remove the problematic BTC account from Ledger Live and add it back with your Ledger device.REMOVE_BTC_ACCOUNT.gif
  4. If the above troubleshooting steps don't work, try adjusting the Coin Control settings in Ledger Live. Please make sure Ledger Live is fully updated before attempting this.

I cleared the cache and my balance decreased

Yes, that happens in some cases. Since this was an issue with the synchronization of your BTC account with the blockchain, it was not displaying the correct balance.

By clearing the cache, you forcefully synced your accounts with the blockchain and you have now the correct balance.
You can verify that by summing up all of your incoming and outgoing transactions related to that account and it will show the same balance. 
This was just a visual glitch and your funds on the blockchain were always of the same value. 

Are you still getting errors?

If you are still getting a "bad-txns-missingorspent" error after trying these solutions, please reach out to our Support Team.

Was this article helpful?