You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/descriptors.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,6 +143,14 @@ are lexicographically ordered as described in BIP67.
143
143
144
144
For a good example of a basic M-of-N multisig between multiple participants using descriptor
145
145
wallets and PSBTs, as well as a signing flow, see [this functional test](/test/functional/wallet_multisig_descriptor_psbt.py).
146
+
147
+
Disclaimers: It is important to note that this example serves as a quick-start and is kept basic for readability. A downside of the approach
148
+
outlined here is that each participant must maintain (and backup) two separate wallets: a signer and the corresponding multisig.
149
+
It should also be noted that privacy best-practices are not "by default" here - participants should take care to only use the signer to sign
150
+
transactions related to the multisig. Lastly, it is not recommended to use anything other than a Bitcoin Core descriptor wallet to serve as your
151
+
signer(s). Other wallets, whether hardware or software, likely impose additional checks and safeguards to prevent users from signing transactions that
152
+
could lead to loss of funds, or are deemed security hazards. Conforming to various 3rd-party checks and verifications is not in the scope of this example.
153
+
146
154
The basic steps are:
147
155
148
156
1. Every participant generates an xpub. The most straightforward way is to create a new descriptor wallet which we will refer to as
0 commit comments