Need help > Standar Mobile Wallet asks for message verification

[mfinos]

Hi everyone, hope you are all doing fine. I am reaching out to request your advice with a problem I am facing with my mobile Electrum Wallet.

It's an old standar wallet, set-up back in 2018 if recall correctly. The problem is, when I try to withdraw funds the wallet is asking for a co-signer to verify the transaction message, and I cannot seem to do this. I've tried verifying with other wallets but it's no use.

As I understand, this is not supposed to happen with standard wallets, am I right? Has anybody run into this scenario? If so, how did you resolve the problem?

Thank you so much in advance for your time!

[Charles-Tim]

It is not a standard (singlesig) wallet.

It is a multisig wallet. That is the reason. You need the required cosigners to also sign the transaction by passing them the partially signed bitcoin transaction before the transaction can be broadcasted to the mempool.

[Mia Chloe]

Just like Charles Tim mentioned, it simply means that back in the day you actually created a wallet which obviously isn't the regular standard Electrum wallet but a multi signature wallet. That co-signer is actually an additional signer for every valid transaction to be fully signed and broadcasted to the Blockchain.
Multi signature wallets are not set with a fixed number multi signature wallets or a fixed number of signers. Last I checked I think Electrum allows upto 20 parties involved in the multi signature wallet creation so you need to recall the minimum number of cosigners you set to all a valid transaction.

[mfinos]

Hi Charles-Tim, thank you for your reply! Still, I can confirm this is in fact a standard wallet (I will post a screenshot shortly to clarify).. this is what's odd here. I was always able to move funds with no verification, untill I last updated the wallet, and it's requesting verification ever since.

Any thoughts?

[BitMaxz]

Hi Charles-Tim, thank you for your reply! Still, I can confirm this is in fact a standard wallet (I will post a screenshot shortly to clarify).. this is what's odd here. I was always able to move funds with no verification, untill I last updated the wallet, and it's requesting verification ever since.

Any thoughts?

Do you remember what version of Electrum mobile it was before? And how did you updated it?

If you downloaded the latest version from a source other than electrum.org you might updated it to a fake Electrum wallet.

Since you mention it was a wallet in 2018, and possible your wallet version before you updated it today is 3.3.2 or below that was released on 2018-12-21, there's a phishing attack on Electrum servers that's pushing you to update your Electrum to a fake Electrum wallet.
3.3.4 below are vulnerable to phishing attacks.

[notocactus]

It's an old standar wallet, set-up back in 2018 if recall correctly. The problem is, when I try to withdraw funds the wallet is asking for a co-signer to verify the transaction message, and I cannot seem to do this. I've tried verifying with other wallets but it's no use.

As I understand, this is not supposed to happen with standard wallets, am I right? Has anybody run into this scenario? If so, how did you resolve the problem?

Its  a multisig wallet, not single signature wallet.

Creating a multisig wallet with Electrum.

Multisig wallet was release in 2015, with Electrum 2.0 version, so if you create your wallet with Electrum in 2018, it's high chance that you did created a multisig wallet.

Electrum releases version 2.0 with 2FA, Multisig wallets and more.

See release note for 2.0 version.

# Release 2.0

 * Support for Multisig wallets using parallel BIP32 derivations and
   P2SH addresses ("2 of 2", "2 of 3").

[nc50lc]

Still, I can confirm this is in fact a standard wallet (I will post a screenshot shortly to clarify).. this is what's odd here.

Please include the source where you've downloaded the mobile Electrum wallet and include the wallet details window as well.
If from Playstore, show the app's Playstore page
If sideloaded, show the source. Plus in this case, you can verify it if it's legit (use a PC to verify)

If those check-out including your screenshot, you may choose to identify if it's a Bug so that the developers can fix it.
If you don't want to, just restore your seed phrase to a new standard wallet, it should work if it indeed "Standard" (Native Segwit / Legacy) and the restored wallet should work.
(those are only if it checks-out, if Electrum is legit)

You're not the only person who reported similar to this but most of those threads have either vague recollection of how it's created or has no reply from OP.
Three of those similar topics (most of those could be using a watch-only wallet):

• https://bitcointalk.org/index.php?topic=5483847.0
• https://bitcointalk.org/index.php?topic=5519722.0
• https://bitcointalk.org/index.php?topic=5516503.0

One similar topic with more useful information including screenshots:

• https://bitcointalk.org/index.php?topic=5517724.20

[satscraper]

Hi everyone, hope you are all doing fine. I am reaching out to request your advice with a problem I am facing with my mobile Electrum Wallet.

It's an old standar wallet, set-up back in 2018 if recall correctly. The problem is, when I try to withdraw funds the wallet is asking for a co-signer to verify the transaction message, and I cannot seem to do this. I've tried verifying with other wallets but it's no use.

As I understand, this is not supposed to happen with standard wallets, am I right? Has anybody run into this scenario? If so, how did you resolve the problem?

Thank you so much in advance for your time!

Do you know SEED relevant to this wallet?  ^{I'm asking because there is a chance that you set up 2FA for the wallet back in 2018.} If yes, try to create new by wallet importing  that SEED and disable 2FA opt. If such scenario doesn't help then your wallet is the standard multisig and your the signature from second cosigner probably your own one. Try to recollect what your other wallet could act as the second cosigner.

[NotATether]

Also we need to know what character the addresses starts with (1, 3, or bc1q), if it's 1 then it's definitely not a multisig wallet. If it's 3 then it is *probably* a multisig wallet unless you used a BIP39 mnemonic phrase and a custom derivation path (unlikely), but if it's bc1 then it could be either - but multisig bc1 addresses are significantly longer than normal bc1 addresses. In any case, if it's a bc1 just measure the length of the address and post the number of characters here so I can cross-check.

[mfinos]

Good day everybody, sorry for the delay, had a bit of a rough week.

First of, I want to say a big thank you to all the people that took a minute of their time and offered their help replying to this topic, thank you so much, I truly appreciate you.

Here's a screenshot of the wallet details:

https://i.postimg.cc/s28vV4v0/SSEW01.jpg

Bitcoin address used: 13tu...

And here's the Playsotre source from which I updated:

https://i.postimg.cc/VN5JQVLC/SSEW02.jpg


I will try and setup the wallet again using the seed, and see if this solves the problem. Hopefully I can work this out and this post helps other users.

Thank you all, have a nice day!

[nc50lc]

And here's the Playsotre source from which I updated:

Looks like the correct PlayStore version link.
There's no typo in the "Electrum Technologies GmbH" developer name.

Here's a screenshot of the wallet details:

This screenshot looks normal but the "Encrypted" icon is missing which shouldn't ever happen in the Android version since it's not possible to create an non-encrypted mobile QML Electrum wallet.
It is similar to the issue in the last linked thread in my previous reply.

I will try and setup the wallet again using the seed, and see if this solves the problem. Hopefully I can work this out and this post helps other users.

When doing that, do not delete your current malfunctioning wallet in case something is wrong with the derivation of the seed.

[mcdouglasx]

I will try and setup the wallet again using the seed, and see if this solves the problem. Hopefully I can work this out and this post helps other users.

To avoid complications and derivation errors with the old seed, you can play it safe by exporting your respective private key in Electrum Mobile and importing it into Electrum for desktop.

Select the Address: Find the specific address you want to extract the private key for.

Show Private Key:

tap on the three dots (menu) in the top-right corner and select "Private key".


you would import it into Electrum for desktop like this:

'create new wallet'

'import bitcoin addresses or private keys'

paste your WIF like this: p2pkh:L5F7qh9JcHVWP1RiNBQ4a90000000000000000000000000000

[nc50lc]

To avoid complications and derivation errors with the old seed, you can play it safe by exporting your respective private key in Electrum Mobile and importing it into Electrum for desktop.

Don't worry about derivations,
Electrum's seed phrase isn't like BIP39 where the user has to remember the derivation path and script type.

Once he typed it during restore, Electrum will automatically detect which script type to use with the "version number" computed from the seed phrase.
Even old type Electrum seed can be detected by the newest client version.

[Pmalek]

I would leave Electrum alone for now. Something is not working as it should. It's good that you can still open the wallet on your phone and hopefully you can see your seed by clicking on the 'Tap to Show Seed' button. If you can, import it into Blue Wallet. It's a good alternative to Electrum, and it supports Electrum-native seeds. I actually prefer Blue Wallet over Electrum on my Android. See if you can make transactions without being asked for co-signers on Blue Wallet.