I didn't take it neither buying it. It's mine...
Hmm, if that's the case, the wallet must be trying to spend the "
unspent txn outputs" of a watch-only address(es) that was included that to your spendable balance somehow.
Otherwise, you'll get a different error or the GUI won't be able to select that UTXO. Never heard or that before though.
Or it what's been said before, the wallet was corrupted/tampered.
To display your "
real balance", start Bitcoin Core with
-zapwallettxes argument (
if your node is pruned, don't),
that will remove all your wallet's transactions and then it will rescan the Blockchain to get the "
real" or updated transactions.
Note:
Backup your wallet before doing so if you didn't have one; and rescanning may take a while (
hours) to finish.
If you're on Windows, create a shortcut, open 'properties' and add
-zapwallettxes at the end of 'Target', eg:
"C:\Program Files\Bitcoin\bitcoin-qt.exe" -zapwallettxes
If you're using Linux, I believe that you have the capability to add start parameters.
So there's no way that he can create a transaction with those as inputs without going though the console/RPC.
Given his technical knowledge (and the errors' behavior), he must have created the transaction though the GUI.
Will it work if i try transferring through Console, what's the command?
No, What I'm saying is the GUI won't use any watching-only 'balance' to create a transaction.
In the console, you have the capability to do so, so that's the only way to make a transaction that will encounter that error when you're trying to sign.
But I saw that you didn't, so your wallet must have included a non-wallet-related transaction(s) into your total spendable balance.
