Transaction error: bad-txns-inputs-missingorspent with incorrect explorer balances

5 replies 235 views
tom.satoshiFull Member
Posts: 87 · Reputation: 549
#1Jul 12, 2020, 07:10 PM
Hey, sorry for the awkward title. Not sure how to phrase it. So, I'm on testnet and using the Unisat wallet extension for Chrome. I created a new wallet today and added some tBTC. I sent some to a few different wallets, but now I can't make any more transactions because of that error message. Plus, I can’t send from one of the wallets I sent tBTC to. I think I get what that 'error: bad-txns-inputs-missingorspent' means, like I’m trying to send tBTC that I don’t actually have. But that doesn’t really make sense since I only sent small amounts of what I initially deposited this morning. I checked the block explorer and noticed that the 'Total Sent' and 'Total Received' figures are way higher than what I've actually put in, and none of those transactions match those numbers. My balance looks fine, but the sent and received values are completely off. I looked over all 7 transactions and didn’t see anything wrong. I really don’t think I sent a bad txn or anything. Here’s my wallet: https://mempool.space/testnet/address/tb1q0puk6v8sm8zhcteyfm707f740g99kwztn7n57k I thought it would sort itself out after a few blocks, but it’s still acting up even after several hours. I can't figure out why it's still broken. If anyone has any ideas on how to fix this or at least understand what's going on, I’d really appreciate it. Thanks a lot!
7 Reply Quote Share
tom.satoshiFull Member
Posts: 87 · Reputation: 549
#2Jul 12, 2020, 10:30 PM
thanks I will try that now.... but it seems so strange that on the block explorer it seems wrong too - its a brand new wallet and I added 5.8 tBTC and its reporting received: ‎40.39202354 and sent: ‎34.65246190 makes zero sense to me Like something has been miss spent somewhere
4 Reply Quote Share
cobra_2015Full Member
Posts: 259 · Reputation: 728
#3Jul 13, 2020, 01:52 AM
bad-txns-inputs-missingorspent is a synchronization error that leads to an attempt to send a UTXO-output that was previously spent. to solve the problem, verify the synchronization and remove the transaction causing the problem, either by: Go to advanced, clear activity tab data Restart the browser. If it is Chrome, use the about:restart option Use the coincotrol feature and spend from inputs that are not part of the previous UTXO-output. There are already people who have complained and I think you have asked a question for the same problem, so wait for the team’s response if above steps above do not solve your problem https://github.com/unisat-wallet/extension/issues/154
6 Reply Quote Share
humbleledgerLegendary
Posts: 1027 · Reputation: 6554
#4Jul 13, 2020, 02:30 AM
Go to the block explorer, and CTRL-F "tb1q0puk6v8sm8zhcteyfm707f740g99kwztn7n57k" so your browser highlights the address. That shows what happened: you've sent small amounts several times, and the change was sent back to the original address. That counts as "received" again, and 7 times (almost) 5.8 makes it just over 40 in total.
1 Reply Quote Share
gr3g.0rbitHero Member
Posts: 1025 · Reputation: 2646
#5Jul 15, 2020, 11:12 AM
Just a heads-up to readers and posters of this topic, OP have also opened an issue in Unisat's GitHub repo As of now it still haven't received any reply from the Devs and not yet solved, he spent it in Electrum instead. Link: https://github.com/unisat-wallet/extension/issues/160 @BootsManuva, it would  be useful if you can share a screenshot of the transaction's "inputs (to sign)" here before clicking "Sign & Pay". With it, we can accurately determine which caused the error, whether the transaction included a spent UTXO or their server missing any of the spent UTXO. For the error, I can't reproduce it. The closest I got is the discrepancy between the "Balance" and the "Available (safe to send)" tBTC which sorted out after a few confirmations. It also managed to select the correct inputs as it only allows the "Available" to be spent.
1 Reply Quote Share
cobra_2015Full Member
Posts: 259 · Reputation: 728
#6Jul 15, 2020, 12:26 PM
Update
4 Reply Quote Share

Related topics