Author

Topic: Hex claming - Electrum error cannot sign messages with this type of address p2sh (Read 540 times)

newbie
Activity: 2
Merit: 0
I'm using 2FA.

then it has nothing to do with SegWit!
2FA wallets in Electrum are multi-signature wallets that use multiple keys and there is no defined standard for singing a message from this type of addresses. in other words there is no workaround for it.

Thanks guys, ahh so sounds like not possible in 2FA wallets
legendary
Activity: 3472
Merit: 10611
I'm using 2FA.

then it has nothing to do with SegWit!
2FA wallets in Electrum are multi-signature wallets that use multiple keys and there is no defined standard for singing a message from this type of addresses. in other words there is no workaround for it.
legendary
Activity: 3724
Merit: 1586
restoring from seed won't help. you can't sign with that address type like the site says. you will have to create a new legacy wallet if you want to be able to sign messages. you can do that via file > new/restore, standard wallet and when asked to choose between legacy and segwit choose legacy. obviously this won't help you if claiming this alt coin requires that you have addresses with a history of bitcoin transactions.
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Have you still got your NMEMONIC SEED? It'll be a series of words you wrote down? I think you'll also need your 3rd public key and you'd jus take a new wallet selecting to make a multisig 2 of 3 wallet and putting your seed in there (but I haven't tried it).

newbie
Activity: 2
Merit: 0
Hello I've been using Electrum for a while now and I was reading how you can claim Hex ( https://go.hex.win/claim/ ) with your bitcoin address in Electrum.

However, when I try to sign my address in Electrum, I get the following error "cannot sign messages with this type of address p2sh".
As far as I can gather, this is because my bitcoin is from the seqwit fork and I'm using 2FA.

My question is, has anyone who's in the same situation been able to come with with a workaround to solve this?
Jump to: