<p>The &quot;musig&quot; descriptor function has not been standardized.</p>
<p>These descriptors also don't seem to contain valid key expressions (which need to be hex pubkeys, hex x-only pubkeys, xpubs, xprvs, or WIF keys, possibly combined with origin information or derivation paths).</p>
<p>Also, descriptors currently don't permit spaces inside.</p>

CC BY-SA 4.0
2022-09-14T21:28:57.757Z
I also know a secret passphrase and have a couple very large _public_ strings (printed in the same instructions). Maybe they combine those small strings with the former to create the actual key expressions.
Mercedes
CC BY-SA 4.0
2022-09-14T21:35:26.560Z
I suspect these small strings are just key fingerprints, which the application uses to look up in a database for actual keys.
Pieter Wuille
CC BY-SA 4.0
2022-09-14T21:15:12.863Z
2022-09-14T21:45:27.240Z
2022-09-14T21:45:27.240Z
Pieter Wuille
<p>In here, about these (indentation is mine):</p>
<pre><code>sh(wsh(multi(2, abcdef01/1'/1'/0/*, 23456789/1'/1'/0/*)))#abcdefgh
sh(wsh(multi(2, abcdef01/1'/1'/1/*, 23456789/1'/1'/1/*)))#ijklmnop
   wsh(multi(2, abcdef01/1'/1'/0/*, 23456789/1'/1'/0/*)) #qrstuvwx
   wsh(multi(2, abcdef01/1'/1'/1/*, 23456789/1'/1'/1/*)) #yz012345
       tr(musig(abcdef01/1'/1'/0/*, 23456789/1'/1'/0/*)) #67890abc
       tr(musig(abcdef01/1'/1'/1/*, 23456789/1'/1'/1/*)) #defghijk
</code></pre>
<p>WALLET tells:</p>
<blockquote>
<p>Output descriptors are part of a <strong>developing standard</strong> for Recovery that WALLET_PROVIDER intends to support and is helping grow. Since the standard is in a very early stage, <strong>the list above includes some non-standard elements</strong>.</p>
<p><strong>When descriptors reach a more mature stage, youʼll be able to take your funds from one wallet to another with complete independence</strong>. WALLET_PROVIDER believes this freedom is at the core of Bitcoinʼs promise, and is working towards that goal.</p>
</blockquote>

<output-script-descriptors><musig>
What's not standard in these descriptors?
Mercedes
# What's not standard in these descriptors?

(Asked by: username_0 on 2022-09-14)

In here, about these (indentation is mine):

```
sh(wsh(multi(2, abcdef01/1'/1'/0/*, 23456789/1'/1'/0/*)))#abcdefgh
sh(wsh(multi(2, abcdef01/1'/1'/1/*, 23456789/1'/1'/1/*)))#ijklmnop
   wsh(multi(2, abcdef01/1'/1'/0/*, 23456789/1'/1'/0/*)) #qrstuvwx
   wsh(multi(2, abcdef01/1'/1'/1/*, 23456789/1'/1'/1/*)) #yz012345
       tr(musig(abcdef01/1'/1'/0/*, 23456789/1'/1'/0/*)) #67890abc
       tr(musig(abcdef01/1'/1'/1/*, 23456789/1'/1'/1/*)) #defghijk

```

WALLET tells:

> Output descriptors are part of a **developing standard** for Recovery that WALLET\_PROVIDER intends to support and is helping grow. Since the standard is in a very early stage, **the list above includes some non-standard elements**.
>
> **When descriptors reach a more mature stage, youʼll be able to take your funds from one wallet to another with complete independence**. WALLET\_PROVIDER believes this freedom is at the core of Bitcoinʼs promise, and is working towards that goal.

**Tags:** output-script-descriptors, musig


---

## 1 answers

### Answer by username_1 on 2022-09-14. Score: 2 | Accepted answer

The "musig" descriptor function has not been standardized.

These descriptors also don't seem to contain valid key expressions (which need to be hex pubkeys, hex x-only pubkeys, xpubs, xprvs, or WIF keys, possibly combined with origin information or derivation paths).

Also, descriptors currently don't permit spaces inside.

> **Comments:**
> **username_0**: I also know a secret passphrase and have a couple very large _public_ strings (printed in the same instructions). Maybe they combine those small strings with the former to create the actual key expressions.  
> **username_1**: I suspect these small strings are just key fingerprints, which the application uses to look up in a database for actual keys.  

---

