-
Notifications
You must be signed in to change notification settings - Fork 74
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
Device PSBT Doesn't Work for Multisig #88
Comments
Did you import the multisig wallet to Specter-DIY? To import multisig wallet to DIY you need to go to settings of the wallet in Specter Desktop > Export to hardware - scan it with DIY and confirm adding the wallet. Then the wallet will be able to sign compressed psbt as well. I need to make a note in the UI somewhere... |
Update: by first importing the wallet as a DIY and not a Cobo that fixed the problem. Device PSBT now signs TXs successfully: So the issue in my mind is that DIY will sign a transaction that it's a participant in but isn't a registered wallet. It should throw a warning telling you not to do that (and to register the multisig first), though I can see an argument for allowing advancing users to transact in that case anyway if they want to be #reckless. |
I'm on |
I think there is a warning that you are spending from unknown wallet, but I think we should make it larger - like a separate confirmation screen saying that "multisig wallet is unknown, import it with the QR code" or something. |
There's an indication that it's an unknown wallet, but no indicator on how to make it known. Remember that I was aware of this issue and trying to import it, but the mistake was that I had it designated in Specter-Desktop as an "other" (paper wallet and not a Specter-DIY): My 2 recs:
|
Example of what my DIY returns on signing (this is a
1-of-4
on testnet):I'm not sure if this is a DIY or Desktop issue. Desktop will scan the device QR code from DIY yet still displays 0 signatures (and no error/warning):
![Screen Shot 2020-10-19 at 11 17 37 AM](https://user-images.githubusercontent.com/448644/96478302-23cd7e80-11fd-11eb-9e21-6416bd4654db.png)
Standard PSBT works great though, so perhaps this is more of a UX issue (warn user that this workflow doesn't work and that they need a device PSBT).
The text was updated successfully, but these errors were encountered: