Open user5289361 opened 3 years ago
Ah right... This is in relation to https://github.com/spesmilo/electrum/pull/6293, where ledger started requiring full previous transactions even for segwit inputs. Due to https://github.com/spesmilo/electrum/pull/6198 (and related CVE) most hardware wallets started to require this...
Other forms of transfer (text/USB file) are able to sign transaction correctly via the Ledger Nano S. QR transfer of transaction appears to correctly transfer input and output for transaction, but fails with the above error at signing point.
The reason QR codes behave differently is because specifically for QR codes we don't include the full prev txs; QR codes have a small capacity and for all but the smallest of txs this compromise is needed.
Error when attempting to sign transaction with a Ledger Nano S after transferring unsigned transaction via QR Code to offline computer running Electrum.
Transaction transferred via QR code shows the following error upon attempting to sign with a Ledger Nano S:
Log data provides the following information relating to the error:
Other forms of transfer (text/USB file) are able to sign transaction correctly via the Ledger Nano S. QR transfer of transaction appears to correctly transfer input and output for transaction, but fails with the above error at signing point.
Error log appears to have shown up in the past in relation to [ https://github.com/spesmilo/electrum/issues/3302 ], which relates to offline signing with Ledger Nano S requiring additional information to sign transaction.
This error is occurring with a nested segwit transaction.