You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing out the Jade I extracted a zpub from the Jade using the Green app (Jade Wallet -> Settings -> Settings -> Watch-only -> Standard). Then a built a simple multisig using it, the mater fingerprint, and the derivation path m/48'/0'/0'/2'.
The Jade refused to sign with an error stating a matching pubkey could not be found in the PSBT.
I repeated the same process, instead using Sparrow and the HWI, which resulted in an xpub (despite it being a multisig) and the signing was successful.
Desired Behavior:
Jade should search through all variants x/z/etc pubs and common derivation paths for matching public keys, and proceed with the signing process.
The text was updated successfully, but these errors were encountered:
Really I'd need to see the xpub (or whatever variant) you extracted from Jade, and the PSBT in question.
Again I'm not really clear on what error exactly is being returned, but ofc Jade can only sign an input if it sees something that needs signing. If it doesn't sign it shouldn't error, it should just return the psbt unchanged.
Or are you not passing jade the psbt, but rather the transaction extracted from it ? What app are you using to do the signing ? Was the error "There are no relevant inputs to be signed" ? If so Jade is not being given a psbt, it's being given a transaction and it is not being asked to sign any of the inputs.
Issue:
Description:
Testing out the Jade I extracted a zpub from the Jade using the Green app (Jade Wallet -> Settings -> Settings -> Watch-only -> Standard). Then a built a simple multisig using it, the mater fingerprint, and the derivation path
m/48'/0'/0'/2'
.The Jade refused to sign with an error stating a matching pubkey could not be found in the PSBT.
I repeated the same process, instead using Sparrow and the HWI, which resulted in an xpub (despite it being a multisig) and the signing was successful.
Desired Behavior:
Jade should search through all variants x/z/etc pubs and common derivation paths for matching public keys, and proceed with the signing process.
The text was updated successfully, but these errors were encountered: