This repository has been archived by the owner on Jun 27, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 377
Valid hex cannot be signed with ethereumSignMessage #338
Comments
Is this issue currently being worked on? Curious about the status here, I have users with ERC721 tokens stuck in their Ledger because of this signing issue. This is affecting the personal_sign method in Metamask + Ledger. Metamask + Trezor had a similar issue, but was fixed when they started accepting hex string data: MetaMask/eth-trezor-keyring#16 |
It would be great if Ledger added support for this. |
I agree. Ledger support for this would be very helpful. |
Ledger support to sign hex messages is needed. Is there an eta on resolving this? |
@gre is there any update on this issue? |
@gre Please update. I can't do specific tasks with my ledger device without this. |
any news here? |
Hi, it would be great to have support for hex data here. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to do personal_sign some hex string data using metamask on ledger. There is no callback after I sign it on the ledger device.
The code:
ledgerjs/packages/web3-subprovider/src/index.js
Line 113 in 12b678c
There is currently no way to sign hex messages using ethereumSignMessage.
The text was updated successfully, but these errors were encountered: