bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-08-18 13:26:23 +00:00
Code Issues Releases Wiki Activity

[bip-390]: add hyperlinks to BIPs (327, 380, 389, 32) (#1877)

Browse Source 
* add hyperlinks to BIPs

* Update bip-0390.mediawiki
This commit is contained in:
Kendra Karol Sevilla 2025-06-24 17:26:41 +02:00 committed by GitHub
parent e22eaa5a52
commit f38f6c4e7b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
bip-0390.mediawiki
View File

@ -15,7 +15,7 @@
==Abstract== ==Abstract==
This document specifies a <tt>musig()</tt> key expression for output script descriptors. This document specifies a <tt>musig()</tt> key expression for output script descriptors.
<tt>musig()</tt> expressions take multiple keys and produce an aggregate public key using BIP 327. <tt>musig()</tt> expressions take multiple keys and produce an aggregate public key using [[bip-0327.mediawiki|BIP-327]].
==Copyright== ==Copyright==
@ -23,15 +23,15 @@ This BIP is licensed under the Creative Commons CC0 1.0 Universal license.
==Motivation== ==Motivation==
BIP 327 introduces the MuSig2 Multi-Signature scheme. It is useful to have a way for keys to be used [[bip-0327.mediawiki|BIP-327]] introduces the MuSig2 Multi-Signature scheme. It is useful to have a way for keys to be used
in a MuSig2 aggregate key to be expressed in descriptors so that wallets can more easily use MuSig2. in a MuSig2 aggregate key to be expressed in descriptors so that wallets can more easily use MuSig2.
==Specification== ==Specification==
A new key expression is defined: <tt>musig()</tt>. A new key expression is defined: <tt>musig()</tt>.
In the following sections, the term <tt>KEY</tt> refers to key expressions as defined in BIPs 380 In the following sections, the term <tt>KEY</tt> refers to key expressions as defined in [[bip-0380.mediawiki|BIP-380]]
and 389. and [[bip-0389.mediawiki|BIP-389]].
===<tt>musig(KEY, KEY, ..., KEY)</tt>=== ===<tt>musig(KEY, KEY, ..., KEY)</tt>===
@ -57,8 +57,8 @@ contains child derivation as specified by <tt>/*</tt> or multipath as specified
<tt>/<NUM;NUM;...></tt>, in addition to the same usage restrictions as in the previous section. The KEY expressions <tt>/<NUM;NUM;...></tt>, in addition to the same usage restrictions as in the previous section. The KEY expressions
additionally must be xpubs or derived from xpubs. The aggregate public key is first computed as additionally must be xpubs or derived from xpubs. The aggregate public key is first computed as
described above, with the keys also being sorted after all derivation and prior to aggregation. described above, with the keys also being sorted after all derivation and prior to aggregation.
Then further BIP 32 derivation will be performed on the aggregate public key as described in Then further [[bip-0032.mediawiki|BIP-32]] derivation will be performed on the aggregate public key as described in
[[bip-0328.mediawiki|BIP 328]]. The <tt>/NUM/.../*</tt> following the <tt>musig()</tt> specifies [[bip-0328.mediawiki|BIP-328]]. The <tt>/NUM/.../*</tt> following the <tt>musig()</tt> specifies
the derivation path to be used when deriving from the aggregate public key. <tt>/*</tt> is also the derivation path to be used when deriving from the aggregate public key. <tt>/*</tt> is also
optional. As there is no aggregate private key, only unhardened derivation from the aggregate public optional. As there is no aggregate private key, only unhardened derivation from the aggregate public
key is allowed. Thus these derivation steps cannot contain <tt>/NUMh</tt> or <tt>/NUM'</tt> key is allowed. Thus these derivation steps cannot contain <tt>/NUMh</tt> or <tt>/NUM'</tt>
@ -108,7 +108,7 @@ Invalid descriptors
==Backwards Compatibility== ==Backwards Compatibility==
<tt>musig()</tt> expressions use the format and general operation specified in <tt>musig()</tt> expressions use the format and general operation specified in
[[bip-0380.mediawiki|BIP 380]]. As these are a set of wholly new expressions, they are not compatible [[bip-0380.mediawiki|BIP-380]]. As these are a set of wholly new expressions, they are not compatible
with any implementation. However the keys are produced using a standard process so existing software with any implementation. However the keys are produced using a standard process so existing software
are likely to be familiar with them. are likely to be familiar with them.