Author

Topic: Electum error signing a message (Read 119 times)

newbie
Activity: 20
Merit: 35
April 27, 2023, 01:49:04 PM
#8
This is a regression in 4.4.0 (and 4.4.1). Fixed now on master.
Please report similar bugs on github.
legendary
Activity: 2394
Merit: 5531
Self-proclaimed Genius
April 25, 2023, 12:37:35 AM
#7
-snip- but I get the following error:


EDIT: Managed to get it done. Once I choose the type of address I wanted, in my case legacy, I changed the bottom parameters from m/44h/0h/0h to m/44/0/0 and it worked fine.
Seems like the issue was the new hardened derivation path scheme which uses "h" instead of " ' ".

Your solution is kind of insecure since you've used non-hardened derivation paths for the "purpose", "coin" and "account" level which should be hardened by the standards.
If you're planning to use the wallet where you'll create a signed message, use this derivation path instead: m/44'/0'/0'
newbie
Activity: 3
Merit: 0
April 23, 2023, 07:20:43 AM
#6
When I go to account and then settings in my ledger live, I only get these options: Export operation history, Export to mobile and Hide empty token accounts. Can't seem to find the Tools tab there or anywhere else...

As far as Electrum goes, I never got to the part where I confirm the sign on the ledger device as I get the error before that.
legendary
Activity: 1512
Merit: 4795
April 23, 2023, 06:43:05 AM
#5
You don't have any other choice but to make a signed message through the ledger live as optional.
For ease, I think no other choice. But for people that can use airgapped device, there is other choice:

If there is urgent need to sign a message with that address and you have done the above and still not able to sign message, follow what BitMaxz posted, or follow this:

If possible you can make yourself an airgapped device by reinstalling your device OS. Import Electrum on it.
Also import offline version of iancoleman: https://github.com/iancoleman/bip39/releases/download/0.5.4/bip39-standalone.html
You will need a text editor for the iancoleman offline version link that I paste above.
Use the text editor to open the offline iancoleman on the airgapped device
Input the seed phrase to get the private key of the bitcoin address that you want to use to sign a message
Open electrum on the airgapped device and import the private key
Then sign the message and it would work.

After you are done, reinstalled the OS of the airgapped device to make everything you have done to be deleted.
legendary
Activity: 3234
Merit: 2943
Block halving is coming.
April 23, 2023, 06:39:46 AM
#4
There is a crash report about this error here below

- https://github.com/spesmilo/electrum/issues/8232

It seems this error not only trigger on signing a message.

Have you selected the check button when confirming the sign message?
If you did then it might be a bug.

You don't have any other choice but to make a signed message through the ledger live as optional.

You can follow this guide How to Sign Message With Ledger Live
newbie
Activity: 3
Merit: 0
April 23, 2023, 05:36:04 AM
#3
I get the message once I click on "sign". I didn't change any parameters as I'm not even sure what they are. I can provide you with my teamviewer ID if it can help to resolve this issue faster.
staff
Activity: 3402
Merit: 6065
April 23, 2023, 05:33:22 AM
#2
Did you export -> manually change -> and import your requests by any chance? There was a similar problem reported not a long time ago: https://github.com/spesmilo/electrum/issues/8232

Are you getting that message when creating a receive request, or when clicking the "Sign message" button? I don't see how you would get it in the latter, since you're not limited to certain characters when signing a message.
newbie
Activity: 3
Merit: 0
April 23, 2023, 05:14:16 AM
#1
Hi, I have a problem signing a message with ledger on electrum. I open the electrum app with my ledger open, choose the standard wallet, then the hardware device option, I get to choose my device and then the legacy address as it is the one I have. I create a receive request and then try to sign a message but I get the following error: "invalid literal for int() with base 10: '44h' " . https://i.ibb.co/SwW7sNN/sc1.png


EDIT: Managed to get it done. Once I choose the type of address I wanted, in my case legacy, I changed the bottom parameters from m/44h/0h/0h to m/44/0/0 and it worked fine.
Jump to: