Skip to content
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

[Bug] Multisig Bluewallet Wallet Descriptor not recognised #486

Open
TimYorke opened this issue Dec 4, 2024 · 3 comments
Open

[Bug] Multisig Bluewallet Wallet Descriptor not recognised #486

TimYorke opened this issue Dec 4, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@TimYorke
Copy link

TimYorke commented Dec 4, 2024

Krux 24.11.1 running on yahboom HW and Bluewallet v7.0.6 (also reproduced on v6.5.5)

I see the error "Invalid wallet: ValueError('invalid wallet format',)" when I try to import the wallet descriptor from BlueWallet (Android). I see the progress bar increase as it recognises the QR codes, but then just displays a black screen with this error message.

I can reproduce it using the QR code animation displayed in "Export Coordination Setup" in BlueWallet, and via "Tools->Descriptor Addresses->Load from camera" in Krux

It's a 2/2 native segwit "Multisig Vault" and derivation path "m/48'/0'/0'/2'"

I'm happy to try and debug locally if someone can give me some pointers.

@TimYorke TimYorke added the bug Something isn't working label Dec 4, 2024
@jdlcdl
Copy link
Collaborator

jdlcdl commented Dec 10, 2024

Would you be able to confirm if you see the cosigner keys as "Zpub" instead of "xpub" in your BlueWallet backup file?

@odudex
Copy link
Member

odudex commented Dec 11, 2024

Your report helped us identify incompatibilities with BlueWallet multisig descriptors and PSBT signing in Krux. We’ve released a fix in v25.01.beta3, which should allow you to successfully load your descriptor and sign PSBTs.

A stable release containing this fix is planned for next month. After not been testing with Blue recently, we will now do more tests and continue to improve compatibility. In the meantime, if you prefer to stick with the current stable release, you can try recreating your wallet in BlueWallet by exporting only the xpubs. This approach should help you avoid the issue until the stable fix is available.

@TimYorke
Copy link
Author

Thank you. The xpub-only workaround did the trick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants