Signing Transaction Failed ( 0,5 btc reward for fixing answer)

[wesjuhnl]

How does that private key look like?

Does it begin with 5 and have ~51 characters?

I recommend you to go to https://www.bitaddress.org/ choose tab "Wallet Details" and enter the private key you have.

Check if you can decode it there. If you can, try importing to a blockchain.info wallet what you get under "Private Key WIF".

If it still fails, let us know in what step and with what output.

Yes it start with a 5 an has 51 or 52 characters.

I went to bitadress.org put in private key in wallet details.

It says in private key wif all zero's

[1715553699]

1715553699

[1715553699]

1715553699

[1715553699]

1715553699

[1715553699]

1715553699

[EcuaMobi]

Then I think there was some error while exporting that private key.

You should double check steps described by: Kouye
https://bitcointalk.org/index.php?topic=354762.msg3810656#msg3810656

Or try running this command before those described by him:
walletpassphrase "your walletpassphrase here" 600

[wesjuhnl]

Then I think there was some error while exporting that private key.

You should double check steps described by: Kouye
https://bitcointalk.org/index.php?topic=354762.msg3810656#msg3810656

Or try running this command before those described by him:
walletpassphrase "your walletpassphrase here" 600

I used walletpassphrase 600 before dumping the key.

[wesjuhnl]

Nobody ?

Guess 2.08 bitcoins waisted then..

[CIYAM]

Nobody ?

I think you are at the stage of needing to grep through the source to work out where that error comes from.

Possibly you might be looking at a corrupted wallet but you might want to check it out a little further before giving up.

[Kouye]

I sent a pm to jackjack pointing to this thread, hopefully he can help with NPW.
I'm not sure he'll have time or be willing, though, so don't expect too much.

[Mitchell]

This is one interesting case. An exported private key that cannot be imported and a wallet that doesn't sign, that does sound like a corrupted wallet. Going to follow this.

[wesjuhnl]

This is one interesting case. An exported private key that cannot be imported and a wallet that doesn't sign, that does sound like a corrupted wallet. Going to follow this.

The private key has been imported into my wallet, but after this i cannot send my coins anymore.

Also i cannot dumpprivkey and import into other wallet because that gives an error.

So basicly my coins are in my current wallet but somehow i cant send them, and i cannot import the private key into an other wallet anymore.

[Dare]

The private key has been imported into my wallet, but after this i cannot send my coins anymore.

Also i cannot dumpprivkey and import into other wallet because that gives an error.

So basicly my coins are in my current wallet but somehow i cant send them, and i cannot import the private key into an other wallet anymore.

Is your wallet encrypted? If so, try this:

launch your bitcoin client as usual and wait for it to load the blockchain and start up
click on 'help' in the menu bar (top right)
click on 'debug window'
select the 'console' tab
type: walletpassphrase <Your actual passphrase here> 600
type: dumpprivkey [your public key here]
this will return the private key, you can copy it now; ensure you clear your clipboard/history afterwards
type: walletlock

Typing "walletpassphrase 600" doesn't work if your passphrase isn't "600". Try the above, but replace the red text with your actual passphrase.

If your wallet's not encrypted, you can skip the "walletpassphrase" and "walletlock" steps.

If that still doesn't work, I'd suggest a rescan of the blockchain (close bitcoin-qt and run "bitcoin-qt --rescan" on the command line, it'll take a while to start). Try rebooting your computer too, that can solve a lot of problems.

EDIT: Forgot the wallet timeout

[wesjuhnl]

The private key has been imported into my wallet, but after this i cannot send my coins anymore.

Also i cannot dumpprivkey and import into other wallet because that gives an error.

So basicly my coins are in my current wallet but somehow i cant send them, and i cannot import the private key into an other wallet anymore.

Is your wallet encrypted? If so, try this:

launch your bitcoin client as usual and wait for it to load the blockchain and start up
click on 'help' in the menu bar (top right)
click on 'debug window'
select the 'console' tab
type: walletpassphrase <Your actual passphrase here>
type: dumpprivkey [your public key here]
this will return the private key, you can copy it now; ensure you clear your clipboard/history afterwards
type: walletlock

Typing "walletpassphrase 600" doesn't work if your passphrase isn't "600". Try the above, but replace the red text with your actual passphrase.

If your wallet's not encrypted, you can skip the "walletpassphrase" and "walletlock" steps.

If that still doesn't work, I'd suggest a rescan of the blockchain (close bitcoin-qt and run "bitcoin-qt --rescan" on the command line, it'll take a while to start). Try rebooting your computer too, that can solve a lot of problems.

I cannot use walletpassphrase yourpasshere without the 600 i get an error then :

walletpassphrase <passphrase> <timeout>
Stores the wallet decryption key in memory for <timeout> seconds. (code -1)

[Dare]

...

Is your wallet encrypted? If so, try this:

launch your bitcoin client as usual and wait for it to load the blockchain and start up
click on 'help' in the menu bar (top right)
click on 'debug window'
select the 'console' tab
type: walletpassphrase <Your actual passphrase here> 600
type: dumpprivkey [your public key here]
this will return the private key, you can copy it now; ensure you clear your clipboard/history afterwards
type: walletlock

Typing "walletpassphrase 600" doesn't work if your passphrase isn't "600". Try the above, but replace the red text with your actual passphrase.

If your wallet's not encrypted, you can skip the "walletpassphrase" and "walletlock" steps.

If that still doesn't work, I'd suggest a rescan of the blockchain (close bitcoin-qt and run "bitcoin-qt --rescan" on the command line, it'll take a while to start). Try rebooting your computer too, that can solve a lot of problems.

I cannot use walletpassphrase yourpasshere without the 600 i get an error then :

walletpassphrase <passphrase> <timeout>
Stores the wallet decryption key in memory for <timeout> seconds. (code -1)

Sorry, I forgot about the timeout. The command you want is "walletpassphrase <Your actual passphrase here> 600". Bitcoin-qt should show a lock icon in the lower right corner of the main window, it will show as an open lock once when wallet is successfully locked. It will automatically lock again after 10 minutes or when you use the "walletlock" command, whichever is first.

[wesjuhnl]

...

Is your wallet encrypted? If so, try this:

launch your bitcoin client as usual and wait for it to load the blockchain and start up
click on 'help' in the menu bar (top right)
click on 'debug window'
select the 'console' tab
type: walletpassphrase <Your actual passphrase here> 600
type: dumpprivkey [your public key here]
this will return the private key, you can copy it now; ensure you clear your clipboard/history afterwards
type: walletlock

Typing "walletpassphrase 600" doesn't work if your passphrase isn't "600". Try the above, but replace the red text with your actual passphrase.

If your wallet's not encrypted, you can skip the "walletpassphrase" and "walletlock" steps.

If that still doesn't work, I'd suggest a rescan of the blockchain (close bitcoin-qt and run "bitcoin-qt --rescan" on the command line, it'll take a while to start). Try rebooting your computer too, that can solve a lot of problems.

I cannot use walletpassphrase yourpasshere without the 600 i get an error then :

walletpassphrase <passphrase> <timeout>
Stores the wallet decryption key in memory for <timeout> seconds. (code -1)

Sorry, I forgot about the timeout. The command you want is "walletpassphrase <Your actual passphrase here> 600". Bitcoin-qt should show a lock icon in the lower right corner of the main window, it will show as an open lock once when wallet is successfully locked. It will automatically lock again after 10 minutes or when you use the "walletlock" command, whichever is first.

Iv done all this before, i can dumpprivkey and i get the code but i cannot import that into another wallet or blockchain wallet. I get an error.

[Dare]

...

Iv done all this before, i can dumpprivkey and i get the code but i cannot import that into another wallet or blockchain wallet. I get an error.

Have you tried removing the passphrase and importing the unencrypted wallet into blockchain.info? I've never imported a wallet.dat there, so I don't know how it handles them.

The only other things I can think of that could be the problem is that either you copied the key wrong and it's missing a character (I've done that before), you're using the public address instead of the private key (unlikely, private key starts with a 5, bitaddress.org can give you an example and it's pretty obvious) or that all your coins are in a change address and blockchain.info won't sweep an empty key (bitaddress.org would have worked, though, so it's probably not that).

Have you tried telling bitcoin-qt to rescan the blockchain yet? If so, did it give any errors, and how long did it take?

Also, can you post the public address here? DON'T post the private key, just the address you use to receive funds for that wallet (e.g. 1M8oUcBnkRDEhWWgV8ZXLTB6p1mgnejVbX).

[starik69]

I went to bitadress.org put in private key in wallet details.

It says in private key wif all zero's

Is your private key 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAbuatmU ? lol

[deepceleron]

The error comes from wallet.cpp:

Code:

                // Sign
                int nIn = 0;
                BOOST_FOREACH(const PAIRTYPE(const CWalletTx*,unsigned int)& coin, setCoins)
                    if (!SignSignature(*this, *coin.first, wtxNew, nIn++))
                    {
                        strFailReason = _("Signing transaction failed");
                        return false;
                    }

SignSignature is two functions, the former is called, and the False status is returned by the final VerifyScript call.

Code:

bool SignSignature(const CKeyStore &keystore, const CScript& fromPubKey, CTransaction& txTo, unsigned int nIn, int nHashType)
{
    assert(nIn < txTo.vin.size());
    CTxIn& txin = txTo.vin[nIn];

    // Leave out the signature from the hash, since a signature can't sign itself.
    // The checksig op will also drop the signatures from its hash.
    uint256 hash = SignatureHash(fromPubKey, txTo, nIn, nHashType);

    txnouttype whichType;
    if (!Solver(keystore, fromPubKey, hash, nHashType, txin.scriptSig, whichType))
        return false;

    if (whichType == TX_SCRIPTHASH)
    {
        // Solver returns the subscript that need to be evaluated;
        // the final scriptSig is the signatures from that
        // and then the serialized subscript:
        CScript subscript = txin.scriptSig;

        // Recompute txn hash using subscript in place of scriptPubKey:
        uint256 hash2 = SignatureHash(subscript, txTo, nIn, nHashType);

        txnouttype subType;
        bool fSolved =
            Solver(keystore, subscript, hash2, nHashType, txin.scriptSig, subType) && subType != TX_SCRIPTHASH;
        // Append serialized subscript whether or not it is completely signed:
        txin.scriptSig << static_cast<valtype>(subscript);
        if (!fSolved) return false;
    }

    // Test solution
    return VerifyScript(txin.scriptSig, fromPubKey, txTo, nIn, SCRIPT_VERIFY_P2SH | SCRIPT_VERIFY_STRICTENC, 0);
}

bool SignSignature(const CKeyStore &keystore, const CTransaction& txFrom, CTransaction& txTo, unsigned int nIn, int nHashType)
{
    assert(nIn < txTo.vin.size());
    CTxIn& txin = txTo.vin[nIn];
    assert(txin.prevout.n < txFrom.vout.size());
    const CTxOut& txout = txFrom.vout[txin.prevout.n];

    return SignSignature(keystore, txout.scriptPubKey, txTo, nIn, nHashType);
}

That's all fun, but I think the problem here is there is garbage bytes written over the wallet.dat, or the berkeleydb store is corrupted, such as pointing to the wrong disk area for information. Time to rename this wallet and restore your wallet.dat backup, easy.

Oh, no backup... Well, make a backup now: copy the wallet.dat you've got to a backup filename. Then restart bitcoin with the -salvagewallet option to scrape wallet information into a new database.