Bitcoin Forum
May 11, 2024, 11:35:32 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Signing issue Electrum  (Read 161 times)
Haputa (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
December 22, 2017, 12:08:34 PM
 #1

Hi there,

I am trying to resolve a stuck transaction through the double spend method, guided by mocacinno in his help thread (https://bitcointalk.org/index.php?topic=1943939.160).

He has created a transaction for me with a higher fee that should replace the old transaction when I sign and broadcast it. I am using Electrum to do these last steps, but I am encountering an issue that mocacinno also doesn't know the answer to. I am hoping someone on this subforum could help us find out what we should do differently.

I have created a .txn file with the following data:

Quote
{
    "final": false,
    "complete": false,
    "hex": "0100000001d45343bf472dcb8ca243daccf39b49399065e52bc310068641609cb48f24433c00000 00000ffffffff0240c7130d000000001976a914ed7de5536a51adb2ffa6a8550754b031d73fe19e 88ac1ef161000000000017a91461b10fa7361e7e62285a03532263790541f563d58700000000"
}

In Electrum, I load the transaction, but for some reason it already says 'Status: Signed' and the Sign button is greyed out. Tried both online and offline.

Anyone here knows what's going on, why it says already signed? Any help is very much appreciated!


Kind regards,
Haputa
1715470532
Hero Member
*
Offline Offline

Posts: 1715470532

View Profile Personal Message (Offline)

Ignore
1715470532
Reply with quote  #2

1715470532
Report to moderator
1715470532
Hero Member
*
Offline Offline

Posts: 1715470532

View Profile Personal Message (Offline)

Ignore
1715470532
Reply with quote  #2

1715470532
Report to moderator
1715470532
Hero Member
*
Offline Offline

Posts: 1715470532

View Profile Personal Message (Offline)

Ignore
1715470532
Reply with quote  #2

1715470532
Report to moderator
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
pooya87
Legendary
*
Offline Offline

Activity: 3444
Merit: 10558



View Profile
December 23, 2017, 06:18:07 AM
 #2

you do not need to create a file! simply open your Electrum, and from the menu select Tools > Load transaction > From text
and then just paste the raw unsigned transaction there.

i'm not sure why it is showing 'Status: Signed', that is really strange and it shouldn't do that.

but in any case Electrum will not recognize nor sign this raw unsigned transaction because your ScriptSig field is empty and Electrum needs to know which private key to use for signing the transaction.

Code:
0100000001d45343bf472dcb8ca243daccf39b49399065e52bc310068641609cb48f24433c000000001901ff16fd00af6c62d8114d4a4a1d5b9d5d655ca3cf6b3b9ba1000000000240c7130d000000001976a914ed7de5536a51adb2ffa6a8550754b031d73fe19e88ac1ef161000000000017a91461b10fa7361e7e62285a03532263790541f563d58700000000

use at your own risk.

.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
Haputa (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
December 23, 2017, 10:59:05 AM
 #3

you do not need to create a file! simply open your Electrum, and from the menu select Tools > Load transaction > From text
and then just paste the raw unsigned transaction there.

i'm not sure why it is showing 'Status: Signed', that is really strange and it shouldn't do that.

but in any case Electrum will not recognize nor sign this raw unsigned transaction because your ScriptSig field is empty and Electrum needs to know which private key to use for signing the transaction.

Code:
0100000001d45343bf472dcb8ca243daccf39b49399065e52bc310068641609cb48f24433c000000001901ff16fd00af6c62d8114d4a4a1d5b9d5d655ca3cf6b3b9ba1000000000240c7130d000000001976a914ed7de5536a51adb2ffa6a8550754b031d73fe19e88ac1ef161000000000017a91461b10fa7361e7e62285a03532263790541f563d58700000000

use at your own risk.

Thanks for your reply, pooya87!

I have tried to sign from text, but also here it says Status: Signed.

Just for more info, it also says:
Size: 142 bytes
Fee: unknown
Inputs (1)
and has unknown after the input data
The first output is highlighted yellow.

Hope this tells you a bit more of what's going wrong here.

Edit: also would like to add that this tx was created from MultiBitHD to Kraken, before switching to Electrum during the resolving proces of the stuck tx.
Abdussamad
Legendary
*
Offline Offline

Activity: 3612
Merit: 1564



View Profile
December 24, 2017, 04:38:25 AM
 #4

So you've already created and broadcasted this transaction :https://blockchain.info/tx/3bf2e0fdd4a9ad01b83c679f83c247d019ecfa6f18c4fd075978b2c47075200a but it is unconfirmed due to low fees.
Haputa (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
December 27, 2017, 12:58:36 PM
 #5

So you've already created and broadcasted this transaction :https://blockchain.info/tx/3bf2e0fdd4a9ad01b83c679f83c247d019ecfa6f18c4fd075978b2c47075200a but it is unconfirmed due to low fees.

Yes, we're trying to double spend the transaction (with higher fees) now to get it unstuck.
Haputa (OP)
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
December 31, 2017, 04:18:57 PM
 #6

bump
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!