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
It is extraordinarily difficult to add Jade to an existing quorum of multisig devices.
Description:
When adding a Jade to a multisig quorum managed by Sparrow, it is impossible to transmit a PSBT for signing using QR codes.
Sparrow has a protocol for doing multiple-QR codes to transmit the PSBT.
Every time the Jade scans the PSBT QR code sequence, it scans some of the QR codes then fails with an error saying "invalid psbt".
Current Behavior
The Jade attempts to read the sequential QR codes one time, failing if one or more QR scans fail
Desired Behavior
The Jade should continually scan the QR codes as the sequence repeats and attempt to stitch together the pieces it scans into a valid PSBT -- trying at least 3 cycles but ideally a dozen or even continually.
The text was updated successfully, but these errors were encountered:
The Jade attempts to read the sequential QR codes one time, failing if one or more QR scans fail
Simply not true. What makes you think this is happening ?
'invalid psbt' - I do not see this in the jade codebase. Did you mean "Unsupported QR/PSBT format" if so, this means the Jade has successfully scanned all the QR codes, and the resulting bytes are not a valid PSBT.
Jade does indeed scan the QR codes indefinitely until it has sufficient codes to rebuild the original message. If any codes are missed or error they are just ignored. It does not error if QR codes fail to scan.
Issue:
Description:
When adding a Jade to a multisig quorum managed by Sparrow, it is impossible to transmit a PSBT for signing using QR codes.
Sparrow has a protocol for doing multiple-QR codes to transmit the PSBT.
Every time the Jade scans the PSBT QR code sequence, it scans some of the QR codes then fails with an error saying "invalid psbt".
Current Behavior
Desired Behavior
The text was updated successfully, but these errors were encountered: