user131280: I’m trying to understand the current state of descriptor support for taproot, with a specific focus on multisig wallets (When I say “multisig” I mean k-of-n threshold signing, rather than a schnorr multisignature). I found this PR that introduced taproot descriptors into Core: https://github.com/bitcoin/bitcoin/pull/22051 and it said that support for more interesting scripts had not yet been implemented. Is that still the case, or does anyone know of any docs or examples to do a multisig wallet descriptor?
Thanks!

user47827: At the time of writing (January 2022) there hasn't been a descriptor specified for Schnorr/Taproot multisig (using the new OP_CHECKSIGADD opcode specified in BIP 342) or using the key aggregation scheme MuSig.

(When I say “multisig” I mean k-of-n threshold signing, rather than a schnorr multisignature)

A clarification on terminology. In Bitcoin we generally use "multisig" to refer to n-of-n (n=n) and "threshold" to refer to k-of-n (k<n). MuSig(2) refers to a key aggregation scheme where only one key and one signature go onchain despite there being multiple keys involved offchain. Threshold equivalents of MuSig(2) are being worked on e.g. FROST but are not finalized or as mature as MuSig(2). Neither MuSig(2) or FROST have descriptors specified at the time or writing.
Hence if you want to use a multisig or threshold signature descriptor you would use an existing one e.g. multi or sortedmulti that doesn't support a Schnorr/Taproot multisig. A bit confusingly the multi descriptor does support both multisignature and threshold signatures according to the above definitions but not for Schnorr/Taproot.

131280: <p>I’m trying to understand the current state of descriptor support for taproot, with a specific focus on multisig wallets (When I say “multisig” I mean k-of-n threshold signing, rather than a schnorr multisignature). I found this PR that introduced taproot descriptors into Core: <a href="https://github.com/bitcoin/bitcoin/pull/22051" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/pull/22051</a> and it said that support for more interesting scripts had not yet been implemented. Is that still the case, or does anyone know of any docs or examples to do a multisig wallet descriptor?</p>
<p>Thanks!</p>
 47827: <p>At the time of writing (January 2022) there hasn't been a descriptor specified for Schnorr/Taproot multisig (using the new OP_CHECKSIGADD opcode specified in <a href="https://github.com/bitcoin/bips/blob/master/bip-0342.mediawiki" rel="nofollow noreferrer">BIP 342</a>) or using the key aggregation scheme MuSig.</p>
<blockquote>
<p>(When I say “multisig” I mean k-of-n threshold signing, rather than a schnorr multisignature)</p>
</blockquote>
<p>A clarification on terminology. In Bitcoin we generally use &quot;multisig&quot; to refer to n-of-n (n=n) and &quot;threshold&quot; to refer to k-of-n (k&lt;n). MuSig(2) refers to a key aggregation scheme where only one key and one signature go onchain despite there being multiple keys involved offchain. Threshold equivalents of MuSig(2) are being worked on e.g. FROST but are not finalized or as mature as MuSig(2). Neither MuSig(2) or FROST have descriptors specified at the time or writing.</p>
<p>Hence if you want to use a multisig or threshold signature descriptor you would use an existing one e.g. <code>multi</code> or <code>sortedmulti</code> that doesn't support a Schnorr/Taproot multisig. A bit confusingly the <code>multi</code> descriptor does support both multisignature and threshold signatures according to the above definitions but not for Schnorr/Taproot.</p>
