Transaction from Electrum didn't appear on my Binance account

[Agamykey989898]

Hello, I sent a small part of the mBTC to see if they would come to Binance, that is: I copied the address of the wallet on the Binance exchange. I entered how much mBTC I want to send from Electrum to the exchange. I clicked send and entered the password to confirm this transaction. The fee was charged
After about 15 hours, the transaction became visible in the Electrum transaction list, but the transaction title is highlighted in red. There is also the info "Local" next to it. In the "Send" tab next to the transaction, on the other hand, there is the info "unconfirmed".
This happened while transferring bitcoin from the desktop wallet to the exchange. I did the transaction, but it turned out to be only partially, because it needs a few signatures, and I have "signed 1/2" marked. As a result, I think the transaction hangs somewhere in the network, and I don't really know what to do to send them to the Binance. Any advices? 

[1714328824]

1714328824

[Charles-Tim]

Is it multisig wallet? You will need to transfer the partially signed bitcoin transaction to the other wallet(s) to sign it also. Read this guide:

https://electrum.readthedocs.io/en/latest/multisig.html

When you click on broadcast (OK), you will see this:



Click on 'share' at the lower left side and you will see:

• copy to clipboard
• show as QR code
• save to file

Use any of the three to send the partially sign bitcoin transaction to the cosigner to sign and broadcast the transaction.

[mocacinno]

Charles-Tim is right.

I just wanted to add one extra piece of information for future reference: your transaction is marked as "local", and it needs an extra signature. This means your transaction doesn't hang on the network. As a matter of fact, none of the other nodes on the network probably know anything about your transaction. You need to finalise your transaction (by providing the second signature) and broadcast it to the network to make the other nodes aware of your transaction... So, Binance is doing nothing wrong: they simply do not know about a partially signed transaction since it hasn't actually been broadcasted yet.

At least, that's my takeaway from the information you provided...

[satscraper]

Hello, I sent a small part of the mBTC to see if they would come to Binance, that is: I copied the address of the wallet on the Binance exchange. I entered how much mBTC I want to send from Electrum to the exchange. I clicked send and entered the password to confirm this transaction. The fee was charged
After about 15 hours, the transaction became visible in the Electrum transaction list, but the transaction title is highlighted in red. There is also the info "Local" next to it. In the "Send" tab next to the transaction, on the other hand, there is the info "unconfirmed".
This happened while transferring bitcoin from the desktop wallet to the exchange. I did the transaction, but it turned out to be only partially, because it needs a few signatures, and I have "signed 1/2" marked. As a result, I think the transaction hangs somewhere in the network, and I don't really know what to do to send them to the Binance. Any advices? 

Your wallet is possible 2FA- type which in fact is the multisig one that requires signature from the second cosigner which is external service you must to pay for. If your wallet lacks the fund to pay for this service the wallet will not send transaction, it is not " hangs somewhere in the network," as you said,  the wallet just didn't broadcast it.

If my guess is correct, then you may ignore that transaction, turn you wallet into non-2FA type, and send to Binance again.

From here you can learn how to " Remove 2FA in Electrum and use Standard Wallet instead".

[Agamykey989898]

Thank you so much for all replies. I will check that soon. It can be as you are writing. I was sure that it's a normal wallet, not multisig, but yeah - maybe...

[nc50lc]

-snip- In the "Send" tab next to the transaction, on the other hand, there is the info "unconfirmed".

That is unintended so you can ignore that invoice's status, and it's worth reporting to Electrum's GitHub repo: github.com/spesmilo/electrum/issues

Normally, a local transaction wont be saved as invoice in the 'Send' tab.
I've tested it and found out that when the invoice was "saved" in combination of saving the transaction in history without broadcasting it, the invoice will have a false "unconfirmed" status.
In 2FA wallet's case, aside from the above sentence, it's saved as "unconfirmed" once "Pay...->OK" is clicked without providing any 2fa code and the user saved it to his History tab.

Refer to the 'History' tab for the actual transaction status.

-snip- but the transaction title is highlighted in red.

This is an Electrum feature to show that the transaction is outbound. On the other hand, inbound txns have black text.

I was sure that it's a normal wallet, not multisig, but yeah - maybe...

The wallet type is entirely visible beside the wallet name in the title bar.
e.g.:

• Electrum 4.5.3 - default_wallet [2fa]         <- 2-factor authentication
• Electrum 4.5.3 - default_wallet [2of3]       <- 2-of-3 MultiSig
• Electrum 4.5.3 - default_wallet [standard] <- Standard

[Agamykey989898]

Thank you @nc50lc! Now it's muuch more clear to me. So, starting the process

[Agamykey989898]

Is it multisig wallet? You will need to transfer the partially signed bitcoin transaction to the other wallet(s) to sign it also. Read this guide:

https://electrum.readthedocs.io/en/latest/multisig.html

When you click on broadcast (OK), you will see this:

https://www.talkimg.com/images/2024/03/11/yKBHT.jpeg

Click on 'share' at the lower left side and you will see:

• copy to clipboard
• show as QR code
• save to file

Use any of the three to send the partially sign bitcoin transaction to the cosigner to sign and broadcast the transaction.

Hello, so I did those steps but cannot open other wallet, as I suppose is the one should sign the transaction also. There is this error showing: "Cannot load wallet. Assertion error". I saw it already reported on Electrum's GitHub repo which is connected with the almost newest version of Electrum wallet 4.5.2, I have the newest one 4.5.3. But the thing is, in that repo people wrote that they cannot open the whole program. I can open one of the wallets, create and restore others. What is not possible, opening the one of wallets which I am pretty sure is cosigner. Do you have any idea for that? Download older version of Electrum maybe?
I was trying to restore the other wallet in Electrum app on Android but I don't see the opportunity there to open any file.

Looks like I have 2 signes wallet, multi sig. And making the transaction, two buttons: "Sign" and "Broadcast" are inactive... I read this guide
https://electrum.readthedocs.io/en/latest/multisig.html
but I don't see the option "Send to cosigner", after creating the transaction.

Any idea, please?

[Agamykey989898]

Hello, I sent a small part of the mBTC to see if they would come to Binance, that is: I copied the address of the wallet on the Binance exchange. I entered how much mBTC I want to send from Electrum to the exchange. I clicked send and entered the password to confirm this transaction. The fee was charged
After about 15 hours, the transaction became visible in the Electrum transaction list, but the transaction title is highlighted in red. There is also the info "Local" next to it. In the "Send" tab next to the transaction, on the other hand, there is the info "unconfirmed".
This happened while transferring bitcoin from the desktop wallet to the exchange. I did the transaction, but it turned out to be only partially, because it needs a few signatures, and I have "signed 1/2" marked. As a result, I think the transaction hangs somewhere in the network, and I don't really know what to do to send them to the Binance. Any advices?  

Your wallet is possible 2FA- type which in fact is the multisig one that requires signature from the second cosigner which is external service you must to pay for. If your wallet lacks the fund to pay for this service the wallet will not send transaction, it is not " hangs somewhere in the network," as you said,  the wallet just didn't broadcast it.

If my guess is correct, then you may ignore that transaction, turn you wallet into non-2FA type, and send to Binance again.

From here you can learn how to " Remove 2FA in Electrum and use Standard Wallet instead".

Hello, now I know that my wallet is only multisig, not 2FA-type. I was following the guidance you've linked but during restoring the wallet I got a message which is in this link (I don't know how to post image here, on forum...)
https://zapodaj.net/plik-lmhkRF1nyY
The message which I also shown on the printscreen above was:
Looks like you have entered a valid seed of type "segwit" but this dialog does not support such seeds. If unsure, try restoring as 'Standard wallet'

[lovesmayfamilis]

Hello, now I know that my wallet is only multisig, not 2FA-type. I was following the guidance you've linked but during restoring the wallet I got a message which is in this link (I don't know how to post image here, on forum...)


The message which I also shown on the printscreen above was:
Looks like you have entered a valid seed of type "segwit" but this dialog does not support such seeds. If unsure, try restoring as 'Standard wallet'

So try restoring it as a standard wallet. https://bitcoinelectrum.com/restoring-your-standard-wallet-from-seed/

[nc50lc]

Hello, now I know that my wallet is only multisig, not 2FA-type.

Can you remember how you managed to create a MultiSig wallet in the first place?
Did someone generated it for you?
Because setting-it up isn't as straightforward as creating a standard or 2fa wallet.

To actually spend from your wallet, you'll have to get access to the other cosigner's seed phrase and restore that cosigner wallet.

Some important questions:

• Do you have another seed phrase backup aside from the one you have? (don't share it)
• In your wallet, how many "keystore" does it show in "Wallet->Information"?
• Do you have any other non-custodial wallet (including another Electrum) that supports MultiSig aside from that one?

[Zaguru12]

Hello, now I know that my wallet is only multisig, not 2FA-type. I was following the guidance you've linked but during restoring the wallet I got a message which is in this link (I don't know how to post image here, on forum...)

The message which I also shown on the printscreen above was:
Looks like you have entered a valid seed of type "segwit" but this dialog does not support such seeds. If unsure, try restoring as 'Standard wallet'

That error could be as a result of you restoring through 2FA-type and probably the seed phrase might not be electrum custom. Try to restore using standard. Now that you’re sure it’s a multi sig wallet then you must have another seed phrase back up somewhere for the other co-signer.

If it is a multi sig wallet though you might be restoring a different wallet if you follow through standard, rather it should be through multi sig restoration with the MPKs of other seed phrase know.

Follow nc50lc post above to get those informations out before proceeding

[BitMaxz]

I think he messed up on the time when he created this wallet and I think he made a multi-sig wallet without thinking that the cosigner key was important.
It's possible that during the wallet creation process, he may have randomly pasted a key in the second part where it asks for a cosigner key, and forgot to save it. Same as what happened to me before when I was a newbie and I regret that I deposited some BTC on that wallet and now can't withdraw my BTC funds without the cosigner key.

[Agamykey989898]

Hello, now I know that my wallet is only multisig, not 2FA-type.

Can you remember how you managed to create a MultiSig wallet in the first place?
Did someone generated it for you?
Because setting-it up isn't as straightforward as creating a standard or 2fa wallet.

To actually spend from your wallet, you'll have to get access to the other cosigner's seed phrase and restore that cosigner wallet.

Some important questions:

• Do you have another seed phrase backup aside from the one you have? (don't share it)
• In your wallet, how many "keystore" does it show in "Wallet->Information"?
• Do you have any other non-custodial wallet (including another Electrum) that supports MultiSig aside from that one?

Hey, so I created it on my own, following instructions in the internet. This was kind of easy for me, but it was few years ago, so I don't rememeber it so well how it was working etc.

According to the questions:
I have only one seed phrase...

There are 2 keystore and also in the name of the wallet there is information (2of2) so I understand it's 2 signatures wallet. I have all the keystores.
I do have some other Electrum wallets on my computer and I am pretty sure which one could be the "cosigner" but the thing is I cannot load that one. I posted name of this error. It is showing when I'm trying to open that wallet. It is also reported already


Edit:
I downloaded and checked two older versions of Electrum 4.5.0 and 4.5.2 (the 4.5.1 was not available) and in both of them I was able to open the second wallet, in my opinion "cosigner". It was the one I couldn't open because of the Assertion error I was writing about. But... in that two versions I couldn't open the main wallet because I was getting an info that these versions are to old to open that wallet. So, I installed the newest version and I can open two of these wallets at the same time!  Now I am kindly asking you what should I do to send my coins for Binanceto not mess the whole work... Just follow that https://electrum.readthedocs.io/en/latest/multisig.html#spending? I feel a bit scared now 

[Abdussamad]

That guide is too old. To spend from the multisig wallet go to the send tab of one of the cosigners and create a transaction spending some bitcoin. Then click on pay and set a suitable fee in the window that pops up and click on ok. A transaction preview window will now appear with details about the transaction. Click on share > copy to clipboard in the bottom left of that window. Then close the window and go open the other cosigner wallet file using the file menu. Go to tools menu > load transaction > from text, paste in the transaction and click on load transaction. The transaction preview window will appear again. Check that the fee and output addresses and amounts are what you expect and click on sign. Then click on broadcast.

[Agamykey989898]

That guide is too old. To spend from the multisig wallet go to the send tab of one of the cosigners and create a transaction spending some bitcoin. Then click on pay and set a suitable fee in the window that pops up and click on ok. A transaction preview window will now appear with details about the transaction. Click on share > copy to clipboard in the bottom left of that window. Then close the window and go open the other cosigner wallet file using the file menu. Go to tools menu > load transaction > from text, paste in the transaction and click on load transaction. The transaction preview window will appear again. Check that the fee and output addresses and amounts are what you expect and click on sign. Then click on broadcast.

Thank you. So, I followed the guiding but when I opened the file with transaction on the second wallet I couldn't click on "Sign" because that field was not active. And the transaction on the first wallet is "Unpaid", despite i paid it

Edit: I checked two wallets I was sure are different ones but... they have the same seeds. And I don't have other seed nowhere on the paper. Does it looks like saying goodbye to my potential money?

[nc50lc]

According to the questions:
I have only one seed phrase...

There are 2 keystore and also in the name of the wallet there is information (2of2) so I understand it's 2 signatures wallet. I have all the keystores.
-snip-

Edit: I checked two wallets I was sure are different ones but... they have the same seeds. And I don't have other seed nowhere on the paper. Does it looks like saying goodbye to my potential money?

You said that you've created the wallet, so you just have to remember where the "extended public key" in "keystore 2" came from.
Because a 2-of-2 MultiSig wallet cannot be created without the other cosigner's "Zpub/Ypub" which you must have gotten somewhere.

And since the extended public key format Electrum uses isn't "famous" around other wallets that sticks to "xpub", there's a high chance that it's from another Electrum.

Perhaps it's from the guide that you've followed back then?
Check the article or guide; if so, see if you can ask the author to cooperate with the signing process.

[Agamykey989898]

Thank you, I will check xpub etc. and try to find the guide website I was following. Thank you all for help and advices. I am really much deeper into Electrum and understand its working much better 

[Cricktor]

This is another example of a situation where the wallet creator would've benefited immensely if the wallet setup details had been better documented. For wallet security best practices you should only write down the mnemonic recovery words offline on e.g. paper (use a good notebook which you know are valuable information in).

A 2-of-2-multisig has two signers and there's no redundancy. Every signer needs its own wallet seed and the extended public key of the co-signer. There's no room for error or loosing a part.

I recommend to at least document the following additional details:

• date and time of creation and by whom
• purpose of this wallet
• created by which wallet software or hardware
• derivation path
• details if accounts on derivation level are used, purpose of those accounts (keep this updated if you add accounts later!)
• hint if one or more optional mnemonic passphrases are in use (do not store the optional mnemonic passphrase together with the mnemonic recovery words)
  
• explicitly and clearly numbered mnemonic recovery words (do not shoot yourself later by scrambling the position of the recovery words by any fancy method; you will forget it unless you document it somewhere, but you risk loosing such details)
  
  Make it a habit to document all those details, you will benefit later.
  
  Did I forgot any needful detail to document?

[Abdussamad]

Electrum doesn't really allow you to choose the derivation path for wallets created using an electrum seed. It automatically chooses an appropriate derivation path. So there is no need to document that.