Support UR types and arbitrary wallet vendors #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the https://github.com/jreesun/urtypes library I just released which is essentially a Python port of the KeystoneHQ ur-registry with some tweaks to support parsing Blockchain Commons UR types.
It also refactors some of the QR parsing logic and now encodes the multisig wallet and PSBT QRs in the format they were read in, so that, in theory, Krux should support arbitrary wallet vendors by mirroring back to them data in a format they understand.
Tested with Specter Desktop (for regressions), Blue Wallet, and Sparrow Wallet, and all three vendors' QR codes are able to be received/sent, with the exception of Sparrow which seems to be ignoring Krux's signed PSBT despite (seemingly) parsing it correctly per debug logs. I am investigating this further and will add a separate PR to fix any issues there.