Unusual change path warning #112
Comments
This means sparrow is not passing the utxo tx - is this the latest version of sparrow ? You're connected via USB I assume - ie. not using QR codes ? |
|
Yes, latest version of Sparrow.
No, not a ‘send all.’
Yes, connected via USB.
I was consolidating UTXOs while I moved from Ledger to you guys, without a hitch. However, when I try to consolidate a final few UTXOs in my Jade by sending to myself, I get the errors.
|
|
Related to: #40 The jade does not handle consolidation transactions properly. |
|
In what sense ? The 'unusual path' warning is more of a 'mismatch' between Jade and the app in question - ie. if the app tells Jade that a certain output is our 'change' - but the path is not of the internal chain (ie. is not .../1/n) then Jade issues that warning - same as if the app tells Jade that a certain output is not our change (but is eg a consolidation output back to ourselves) but the path is of the internal chain (ie. .../1/n) then again Jade issues that warning. The error “failed to extract input_tx.” is due to the app not passing Jade the full tx from which the utxo being spent was an output. |
|
Right. As I understand it, the mismatch is due to a bug in HWI, which most apps use to interface with Jade. |
|
I can look at it myself when I get a moment ... |
|
Do you know if resolving the mismatch in HWI would also fix the second issue ( |
|
I don't think so, as I think that implies the psbt being passed from sparrow to hwi/jade is missing some data jade expects. |
|
I am having the same issue, error messages as above when using Sparrow with the Jade to consolidate UTXOs , is there a solution. Any help would be appreciated. |
|
I'm not aware of any workaround at the moment. |
|
Hi Yianni,Thanks for the update. Please keep me posted if there's a fix for this issue. Currently, I can't move funds from Sparrow Wallet due to problems with bulk transactions from Strike, though transactions work from Green Wallet.In Sparrow, the UTXO appeared normal but couldn't be signed because of an error. Additionally, Jade incorrectly reports that the fee is larger than the transaction amount. But the fee is actually significantly lower. The main issue:- Jade displays a warning about an "unusual change path."- Sparrow fails with a "failed to extract input_tx" error.Appreciate any help. Thanks!Cary Hammond Sent on the move On 28 Aug 2024, at 19:37, Yianni Georgantas ***@***.***> wrote:
I'm not aware of any workaround at the moment.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
Oh actually, you can maybe try using an older version of Sparrow. I don’t recall “failed to extract input_tx” being an issue when I had used multisig with the Jade some versions ago. I believe I had used this version: https://github.com/sparrowwallet/sparrow/releases/tag/1.6.4 The unusual change path error will persist however because thats an issue on the Jade’s side. |
|
Hi, Yianni Thank you for the advice I shall try to revert back to an older version of Sparrow. Maybe that might work. The issue was with one UTXO from Strike which was sent when I was using the latest Sparrow update. I’ll try an older version and send a transaction from strike and see if I get the same signing issue. I’m using Green to & that seems fine just in case. Interesting on the unusual change path maybe there will be a fix on a future firmware update. Was the other issue too where Jade shows a message saying that the fee is higher than the send if that makes sense. Which it’s not but I still sign out a transaction fine. Thank you Yianni for your time with this. The Jade is a great little device but you do get confused - concerned when things don’t seem correct 👍 Cary Hammond Sent on the move On 29 Aug 2024, at 00:19, Yianni Georgantas ***@***.***> wrote:
Oh actually, you can maybe try using an older version of Sparrow. I don’t recall “failed to extract input_tx” being an issue when I had used multisig with the Jade some versions ago. I believe I had used this version: https://github.com/sparrowwallet/sparrow/releases/tag/1.6.4
The unusual change path error will persist however because thats an issue on the Jade’s side.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
No, I did not get any fee issues on that version. If you are still having issues with the fee and "invalid input" error on version 1.6.4 of Sparrow, then I think these issues could be related to a newer version of the firmware. I don't think a root cause for them has been identified yet. Agree, these issues do not inspire confidence 😣 |
|
The 'unusual path' warning is more of a 'mismatch' between Jade and the app in question - ie. if the app tells Jade that a certain output is our 'change' - but the path is not of the internal chain (ie. is not .../1/n) then Jade issues that warning - same as if the app tells Jade that a certain output is not our change (but is eg a consolidation output back to ourselves) but the path is of the internal chain (ie. .../1/n) then again Jade issues that warning. The error “failed to extract input_tx.” is due to the app not passing Jade the full tx from which the utxo being spent was an output. |
|
I have recently made a PR to HWI which should address these issues - ofc we have to wait for HWI to take them, release, and then Sparrow to upgrade HWI ... |
|
Hi Jamie very Interesting and thank you for your response. I also want to thank the team at Blockstream, I have had some excellent feedback.
‘Change’ popped up when I was trying to research the issue I was having but did not quite understand at the time.
I also spoke with Craig Raw on Telegramme Funny as at first it was not him and I was given instructions for a fix, well step 2 was to input my seed which of course I did not LOL
Anyway, I did speak with the real man who advised on a driver issue but that did not work. He then advised me to speak with Blookstream.
So Jamie this transaction was a single UTXO from Strike as a bulk send, I have since stopped until I can solve this issue with Sparrow as it was fine when using green.
What would be the advice now Jamie would I just have to wait for Sparrow to upgrade HWI, which I have no idea what that is ha!
Unfortunately the link bitcoin-core/HWI#753. I get a warning from and can't see that page.
Thanks again
… On 5 Sep 2024, at 09:20, Jamie C. Driver ***@***.***> wrote:
The 'unusual path' warning is more of a 'mismatch' between Jade and the app in question - ie. if the app tells Jade that a certain output is our 'change' - but the path is not of the internal chain (ie. is not .../1/n) then Jade issues that warning - same as if the app tells Jade that a certain output is not our change (but is eg a consolidation output back to ourselves) but the path is of the internal chain (ie. .../1/n) then again Jade issues that warning.
The error “failed to extract input_tx.” is due to the app not passing Jade the full tx from which the utxo being spent was an output.
—
Reply to this email directly, view it on GitHub <#112 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKSY56UMAAFIPZVI6PEP4KLZVAH3DAVCNFSM6AAAAABBWWYWDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQHEYDENRVHE>.
You are receiving this because you commented.
|
I didn’t have any issues sending/receiving from other wallets to Jade. However, I’m having trouble consolidating UTXOs within my Jade, using Sparrow.
When I attempt to sign the transaction, Jade warns me of an “unusual change path” and Sparrow reports that it “failed to extract input _tx.”
I have closed Jade in Sparrow and reopened with the correct passphrase, but don’t know what to try next.
The text was updated successfully, but these errors were encountered: