diff options
| author | Ava Chow <github@achow101.com> | 2024-07-09 15:15:13 -0400 |
|---|---|---|
| committer | Ava Chow <github@achow101.com> | 2024-07-09 15:15:13 -0400 |
| commit | c88c3970ed8194a166f783aa748adeb581f79321 (patch) | |
| tree | 6dc59b9d8c93126213767a0ed5c0443ba7210654 | |
| parent | 0a78fc10bdc1c4fb009c6fdb58f011a123bad97b (diff) | |
| download | bips-c88c3970ed8194a166f783aa748adeb581f79321.tar.xz | |
389: Explicitly disallow duplicate multipath
| -rw-r--r-- | bip-0389.mediawiki | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/bip-0389.mediawiki b/bip-0389.mediawiki index 72121b7..6c88a89 100644 --- a/bip-0389.mediawiki +++ b/bip-0389.mediawiki @@ -48,6 +48,7 @@ This is modified to state: When a <tt>/<NUM;NUM;...;NUM></tt> is encountered, parsers should account for a presence of multiple descriptors where the first descriptor uses the first <tt>NUM</tt>, and a second descriptor uses the second <tt>NUM</tt>, and so on, until each <tt>NUM</tt> is accounted for in the production of public keys, scripts, and addresses, as well as descriptor import and export operations. Descriptors that contain multiple Key Expressions that each have a <tt>/<NUM;NUM;...;NUM></tt> must have tuples of exactly the same length so that they are derived in lockstep in the same way that <tt>/*</tt> paths in multiple Key expressions are handled. +Duplicate <tt>NUM</tt>s within a tuple are not allowed. The common use case for this is to represent descriptors for producing receiving and change addresses. When interpreting for this use case, wallets should use the first descriptor for producing receiving addresses, and the second descriptor for producing change addresses. |