Topic: Can't broadcast signed transaction (Read 1011 times)

Do any of those addresses have a red letter U next to them when you check them on blockchain.info? The top address in the example below shows a red letter U to indicate that its inputs are unconfirmed. If one or more of your addresses shows a red letter U then the problem might be due to an unconfirmed input, otherwise the problem's caused by something else.

Hello,


I've started a transaction with Electrum 2.8.2 on Windows. Next I've signed it with Electrum 2.8.2 on Linux, cold storage,  and it looks like the signing processes is successful.  As soon as I try to broadcast it all I am getting this error:

"The transaction was rejected by network rules. (16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation))"

I've connected the PC to Internet and tried one more time to send the coins directly from that wallet. All I get is: "The transaction was rejected by network rules. (16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation))"

As I observed, the coins are stored on three change addresses. One of them is red. Gap was increased. I've tried to add $1 to each of those addresses - the balance is updating.

Next I've tried to sweep the private keys and the only thing I get is "No inputs found (Note that inputs need to be confirmed)"

Is it there any chance to recover those funds?
Thank you in advance. Any advice would be much appreciated.

EDIT: I've noticed a similar thread on reddit. So I am not the only one with the same problem. Hope to get it fixed.

idk how this could help. Basically what I understood is that for some reasons a bitcoin address from my wallet doesn't get it's correct private key. Or vice-versa. Correct me if I am wrong please. 

Hi All!

We have a strange problem with electrum-wallet.

Facts: We have 10 electrum-daemons 2.7.18, which run under different users on one server. JSON-requests to this daemons are balanced by nginx. All works fine about the month (without restart), but recently we wanted to update our wallets to 2.8.2. After command electrum daemon stop balance of 5 wallets out of 10 became 0. Then, i started electrum daemons again, and in 5 of 10 wallets balance became much less than should be.
Ok, I tried to restore this wallets from seed, but, unfortunately, balance was like after reboot.

Investigation: Fortunally, all addresses, which were used for payment requests were stored in 2 places - in wallet_file and on the filesystem. Grep on payment requests showed more than 700 addresses, which were used for this requests, but electrum listaddresses showed me less than 300 addresses.

Next, I took one random address from 700 and said electrum ismine _thisaddress_, result was false. I manually added this address in wallet_file in tag "addresses":"receiving", and after that result of electrum ismine _thisaddress_ became true.

Ok, next I tried to send BTC from this address and received an error: 'code': -26, 'message': '16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation) - this error means "error in sign of transaction". Sending BTC from addresses, restored from seed, was fine.

Next, I tried to export private key of _thisaddress_. It was ok, but, when I tried to import it to new wallet, I saw, that address of this private key did not match with _thisaddress_. I think, that this situation and error: 'code': -26 have one reason.

Next, I exported all 700+ addresses from payment requests, flushed tag "addresses":"receiving" in wallet_file and manually added all this addresses in this tag. After that, I exported all private keys from this wallet and imported them to new wallet. The balance of new wallet became correct and I could send BTC from this addresses.

Question: Why did this happen?

Do any of those addresses have a red letter U next to them when you check them on blockchain.info? The top address in the example below shows a red letter U to indicate that its inputs are unconfirmed. If one or more of your addresses shows a red letter U then the problem might be due to an unconfirmed input, otherwise the problem's caused by something else.

https://s8.postimg.org/hc4fgkr6d/image.png

It doesn't seem to be a problem with his outputs and their confirmation. I have found a similar problem on the repository here: https://github.com/spesmilo/electrum/issues/2242 and the problem seems to be coming from the signing process and the bug should have been fixed in the latest version.

edit: similar https://bitcointalksearch.org/topic/electrum-not-restoring-addresses-from-seed-1849541

the coins are stored on three change addresses.