Skip to content

Commit 9de0d94

Browse files
committed
doc: add disclaimer highlighting shortcomings of the basic multisig example
1 parent f9479e4 commit 9de0d94

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

doc/descriptors.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -143,6 +143,14 @@ are lexicographically ordered as described in BIP67.
143143

144144
For a good example of a basic M-of-N multisig between multiple participants using descriptor
145145
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+
146154
The basic steps are:
147155

148156
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

Comments
 (0)