problems broadcasting on possibly corruped backup file

[troublepk]

hey
so i found on an old hard drive of mine an old electrum wallet backup plus written down all the addresses and private keys. opened it with electrum and everything seemed fine at first but when i tried to move some of the funds i got an error saying "The server returned an error when broadcasting the transaction. Consider trying to connect to a different server, or updating Electrum." Script failed an OP_EQUALVERIFY operation" so i went over to block explorer to broadcast raw and there i get an error " sendrawtransaction RPC error -26: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation)".i tried 3 different transactions always the same. But whats weird if i look now in "sent" on electrum two of them are listed unpaid but one is suddenly listed as unconfirmed.so i tried to use the seed on a different wallet but there i get "invalid seed" and when i tried the private keys, for some of them i get a different address every time. meaning i import a private key into my wallet check address, then delete that wallet again and import the same key again, i suddenly get a different address then the time before.
so yeah if anyone could point me into the right direction  as to where to even start to try and fix this clusterfuck, would be greatly appreciated

[Abdussamad]

so i tried to use the seed on a different wallet but there i get "invalid seed"

By different wallet do you mean other wallet software? Electrum seeds don't work with other wallet software. Try restoring from seed again in electrum by going to file menu > new/restore, enter a unique filename and click ok. Then proceed with on-screen instructions for the rest of it.

[pooya87]

Based on the two information you gave us I can say what you are using is not Electrum software.
That's based on the error message and the fact that you say it is part of your wallet history ("listed as unconfirmed" as you put it). The signature in those transactions has nothing to do with your address based on the error and Electrum would never sign such a tx and even if you had signed it elsewhere and imported it into Electrum, Electrum still shouldn't include it as a valid tx in your history.

Regarding Script failed an OP_EQUALVERIFY operation, basically in P2PKH scheme your signature has to include a signature and a public key (using the same private/public keys that generated your address). Then your output script that starts with OP_DUP OP_HASH160 <your-address-hash160> would first duplicate that public key, hash it then compare it with the 160-bit hash in your output (that encodes your address as well) then checks its equality with OP_EQUALVERIFY operation and fails if the public key had nothing to do with your address. Which is what happened here.

[nc50lc]

opened it with electrum and everything seemed fine at first -snip-

Did Electrum showed you any error when you load the backup wallet file and typed its password?
If so, read it.

Because it should be able to detect if the extended (master) private key cannot derive the xpub at least one of the address in its list,
That usually results with the error that you've mentioned.
My reproduction result:


Restoring the seed should be the first step in issues like that. (unless the wallet backup is forged to show txns that it can't spend)
But make sure to install the correct Electrum binary since a lot of fakes are showing in various search engines.
Only download it from: electrum.org/#download
And verify its signature: bitcoinelectrum.com/how-to-verify-your-electrum-download

-snip- and when i tried the private keys, for some of them i get a different address every time. meaning i import a private key into my wallet check address, then delete that wallet again and import the same key again, i suddenly get a different address then the time before.

Whatever wallet that is, do not use it.
Inconsistent import shouldn't happen in any well-written wallet.