Bitcoin Forum

Huh?? never happend before... reinstalled core wallet and tried one more time but same error "Signed Transaction Failed" press Ok "transaction creation failed" how to fix this i know something is wrong with wallet.dat but not sure how to fix it...

We're gonna need more info than this.
Are you using the GUI or signing through the RPC?

Is your wallet fully synced? Are you sure you're signing inputs for which you have the private keys in your wallet.dat, yadayayada...?

If you think something is wrong with your wallet.dat, it might be smart to make a backup first, and go from there. (https://bitcoincore.org/en/doc/0.16.0/rpc/wallet/dumpwallet/)

The error "transaction creation failed" sometimes happens if you have many small inputs from your wallet they mostly called it dust transactions and the asking fee is not enough due to tons of mini transactions.

Did you get those bitcoins from faucet sites or from a mining pool?

I found a solution from an old thread it seems a bit technical and it seems you need to make a raw transaction to combine or consolidate all dust inputs.
Read this https://bitcointalk.org/index.php?topic=218447.msg2303549#msg2303549

Yes im using GUI.
Unfortunately wallet is not fully synced but i don't believe if this is the cause because when you try to make a transfer while wallet is synchronizing with network it will work but it will be not confirmed until synchronizing is done...

Have you checked the Bitcoin Code debug.log file to see if there is a more detailed error message than simply  "signed transaction failed"? ???

You can find the debug.log in your Bitcoin Core "datadir" (same directory as your wallet.dat file) which should be listed in "Windows -> Information" menu of the Bitcoin Core GUI.... it's a plain text file, so you can just open it with a standard texteditor.

Try recreating the transaction, wait for the error message, then open/refresh the debug.log in your text editor to see what the detailed error message is.

Are you the same person who posted this?: https://bitcoin.stackexchange.com/questions/99988/signing-transaction-failed (https://bitcoin.stackexchange.com/questions/99988/signing-transaction-failed)
If yes (or no), then please consider the dev's answer in stackexchange.

I came with a conclusion that you're the same person because of:

• You were looking for a link of Bitcoin Core 0.9.3 in your previous thread (https://bitcointalk.org/index.php?topic=5288890.msg55580620#msg55580620).
  
• Both posts contents are similar.

Yes im same person in stackexchange thread... but no helpful there at all

Can you tell me the reason why you need to use v0.9.3 instead of the latest?
Because a wallet that was generated by an older version can be upgraded (automatically) to be used by the latest.
That is if you're worried of compatibility issues.

Of course, don't forget to create a backup.

Trying to get private keys from my old wallet but each version i download of bitcoin core i get "private keys for X address not found"

That error must be the same reason of the "Signing Transaction Failed" error that you're getting when trying to spend.
The wallet doesn't have the private key(s) for the UTXOs used by the transaction.
Where did you stored/get the wallet.dat? Was the drive damaged, corrupted or it was from someone else?

Additionally, the keys are in the wallet.dat, I can't find the relation with Bitcoin Core's version,
was the result with v0.9.3 different than other versions that's why you've been using that version?

What do you mean by that?
wallet.dat cannot be longer used and recovered?

I can't totally say yes.
But based from the result, it must be corrupted somewhere or there's "something" in that wallet.dat.

Something like tampered data.

@nc50lc, well spotted!

---

Seems the wallet.dat is either:
1. Corrupted
2. Contains "fake data"
3. or it has one or more "watching-only" addresses imported into it (ie. no private key for the addresses of the UTXOs being spent)

Would advise that you make some copies of the wallet.dat (if you haven't already) to prevent any further corruption of the wallet file... and only work with the copies, not the original file.

Have you tried using dumpwallet from Bitcoin Core to dump the keys from the wallet.dat? ??? If it doesn't show the private key for the address in question, then either it's a watching-only address or the wallet.dat is corrupt/tampered with. Alternatively, you can also try using PyWallet to dump all the keys from the wallet.dat file

I would recommend trying dumpwallet command in Bitcoin Core first.

Yes, but addresses which contains BTC doesn't show up there, i checked one by one but those addresses were 0 BTC.

Then your wallet file does not contain the private keys.

Did you create the wallet file yourself or did you receive it (e.g. by buying it)? All wallet files sold are manipulated. If you bought one, you got scammed and there is nothing you can do about that now.

If you did create it yourself and it is not bought etc., how did you exactly create it? Who gave you the address/private key / where did it come from?

Then, as bob123 has already said, your wallet file simply does not have the appropriate private key to be able to spend those coins.

Either they are on a "watching-only" address (ie. an address was imported into Bitcoin Core using the importaddress command... which means the transactions and balance for that address would show, but would not be spendable... or the file has been manipulated in some way, so that it contains the public key/address that has the BTC, but the private key does not match.

If the wallet file is actually your old file, then it's most likely the importaddress scenario, if you bought or downloaded this wallet.dat online, then it is most likely the 2nd scenario and the wallet file is fake.

It must be a "manipulated wallet" then.
Because a watch-only address' unspent txn outputs can't be selected automatically by Bitcoin core's coin selection algo.
Those are even not available to be selected in the coin-control feature.

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?

In your case: No, most likely not.

Where did get your wallet file from?
If you didn't create it yourself, you got scammed. Every bought wallet is equal to getting scammed.

I didn't take it neither buying it. It's mine...

No, it won't work... because you still won't have the private keys in your wallet to be able to spend the coins. Even though you could manually create the transaction, you won't be able to sign it (because the private keys are not there), so you won't be able to broadcast it to the network. :-\

If you have already done a "reindex" and/or "rescan" then it's most likely that the file is corrupted or has been tampered with. In either case, there is no chance you will be able to recover any coins :-\

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:
If you're using Linux, I believe that you have the capability to add start parameters.

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.