-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
electrum 4.4.0-4.4.2 not working with legacy ledger bitcoin app (pre-2.1): no sig for <compressed_pubkey>
#8365
Comments
What do you mean by not working?
Do you get any specific error message?
Please enable debug logging and attach a debug log. See https://electrum.readthedocs.io/en/latest/faq.html#how-to-enable-debug-logging
What do you mean by "ledger nano"? Original nano? "Nano S"? Nano S plus? Nano X?
What is the version of the bitcoin app on your device?
|
check this tweet https://twitter.com/Edward2100/status/1651547697260666881 is the same for me tested by me with Ledger nano and ledger nano S, electrum v4.4.0 v4.4.1, with v4.3.4 is working I can sign the transaction I will not add any logs from my electrum wallet, sorry but privacy matter for us.. I know I know si safe. maybe not but in the future who knows? EDIT(sombernight): the tweet contains an image with an error popup, saying:
(i.e. |
I was not able to reproduce. |
is still not working, |
Have you tried with 4.4.2 though?
Yes, I have tested with exactly that scenario and it works for me. There are other variables and you still haven't answered all my questions from before, for example:
If it still does not work on 4.4.2, please provide an exception traceback from the debug logs.
Please try to understand that this statement is completely unusable and has approximately zero information value. |
no sig for <compressed_pubkey>
There was another report on bitcointalk now and it specifically said "Ledger Nano S with bitcoin app version 1.6.0". The issue occurs on any modern ledger device when using an old bitcoin app (pre-2.1, I believe). <-- having to use an old bitcoin app was the piece of the puzzle missing before. Below traceback and modified log for a p2wpkh wallet, but the issue affects all script types. It is a regression from 4.4.0 (from #8230).
Here is how that unsigned tx hex looks in 4.3.4:
Apparently we had been giving garbage in past versions in the witness (and scriptSig) to the device, and that worked ok. Based on my testing, with wallets using script types |
I just found out that this same problem is happening with the diy version of jade blocstream, can you tell me which version of electrum can work |
@sandman21vs see #8463 |
Starting from electrum version 4.4.0 ledger won't work but is working fine with version 4.3.4
There is no info to sign the transaction.
The text was updated successfully, but these errors were encountered: