Cannot create Miniscript wallet

[chuber11]

Hello,

I just tried the newest version on Windows and wanted to create a test Miniscript wallet. First, I added the keys. This worked. Then I tried creating the wallet. I entered a taproot descriptor which was parsed correctly, however, on the "Configure wallet" page it is not possible to press the "Continue" button (see screenshot). Any idea what I could try?

[tongvanlinh]

@chuber11 Thanks for your info. We are checking this, we will have another release today

[tongvanlinh]

@chuber11
It seems like you already have a descriptor. For now, please use the "recover wallet using descriptor file" function to create the wallet.

[chuber11]

I tried that but I need a bsms file I don't know how to create (I only have the Taproot descriptor).
I also tried to create a new Miniscript wallet from the templates provided (Decaying multisig), however for Segwit I get the error
Error: [-2010] Signer id cannot be empty!
when clicking "Add existing key"
and for Taproot I cannot select the key (all keys are greyed out) in the "Do you want to add an existing key" window.

[qaNunchuck]

@chuber11 Thank you for your feedback!
Here are some instructions and notes to help you proceed:
How to Recover Your wallet using a descriptor file
You can recover your wallet using a descriptor file by following these steps:

1. Please paste the taproot descriptor into the file and save it as a .txt file
2. Click the + Add wallet icon.
3. On the Create Wallet screen, select Recover existing wallet.
4. Choose the option Recover via BSMS/descriptor.
5. Upload your descriptor file.
6. Name your wallet.
7. Click Continue to complete the recovery process.
   ▶️ Video guide: How to recover a wallet via descriptor file
   https://drive.google.com/file/d/1IT0XWGIVE2-ohN7TwaPQUGNlXOymsv9c/view

Issue when using miniscript wallet templates
When using a new Miniscript wallet from the available templates (e.g., Decaying Multisig for Segwit), you might encounter the following error: [-2010] Signer id cannot be empty!. This occurs when clicking "Add existing key".
✅ Workaround:
Instead of choosing Add existing key, please select Add new key. We are aware of this issue and are working on a fix for the "Add existing key" functionality.

Miniscript taproot wallets – Key support notice
Currently, Miniscript taproot wallets only support software keys.
Because of this, other key types will appear grayed out and cannot be selected. To add a key to a Taproot wallet:

1. On Do you want to add an existing key screen: Click “Take me to add a new key”.
2. Select Software key.
   ▶️ Video guide: How to add a software key to a taproot Miniscript
   https://drive.google.com/file/d/1_BcMqGInlFVUE9KZlDY7z0sn__K2GiPK/view

[chuber11]

I tried to recovery a wallet using the following descriptor:
tr([bed52764/84'/0'/0']XPUB1/<0;1>/,{and_v(v:and_v(v:pk([a70907b7/84'/0'/0']XPUB2/<0;1>/),pk([c86dbe82/84'/0'/0']XPUB3/<0;1>/)),older(1)),and_v(v:multi_a(1,[a70907b7/84'/0'/0']XPUB2/<2;3>/,[c86dbe82/84'/0'/0']XPUB3/<2;3>/*),older(2))})#djz2l980
However, I get
Error: [-1020] Invalid parameters n, m
I also tried replacing <0;1> by 0 and <2;3> by 2 (and updating the checksum), but that gave the same error.
Is this the same problem that Miniscript taproot wallets currently only support software keys?
Do you plan to support hardware keys for Miniscript taproot wallets soon?

[qaNunchuck]

@chuber11 Looks like you exported a Liana wallet that reuses keys. Liana key reuse uses <2;3> paths. Nunchuk currently doesn’t support descriptors containing <2;3> paths.
For key reuse in Nunchuk, we don’t use <2;3> paths but use a new XPUB derived from the same seed phrase.

[hugohn]

@chuber11 We do support hardware signers for Taproot miniscript. Currently there are 2: Coldcard and Ledger.