diff options
| author | Jon Atack <jon@atack.com> | 2024-05-12 10:56:34 -0600 |
|---|---|---|
| committer | Jon Atack <jon@atack.com> | 2024-05-12 11:08:30 -0600 |
| commit | e7fef46177e092b2122abad86d5bd02797a7c98b (patch) | |
| tree | 5b5eb658d909143d2b8ed5091b8860de382e943d | |
| parent | 8256ea013436fb454b5097368ec52e93d804c5df (diff) | |
| download | bips-e7fef46177e092b2122abad86d5bd02797a7c98b.tar.xz | |
bip-0388: fix 3 links
| -rw-r--r-- | bip-0388.mediawiki | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/bip-0388.mediawiki b/bip-0388.mediawiki index 511e27c..93f84bc 100644 --- a/bip-0388.mediawiki +++ b/bip-0388.mediawiki @@ -65,7 +65,7 @@ We set two fundamental design goals: * Minimize the amount of information that is shown on screen - so that the user can actually validate it. * Minimize the number of times the user has to validate such information. -Designing a secure protocol for the coordination of a descriptor wallet among distant parties is also a challenging problem that is out of scope in this document. See [[bip-00129.mediawiki|BIP-129 (Bitcoin Secure Multisig Setup)]] for an approach designed for multisignature wallets. Regardless of the approach, the ability for the user to carefully verify all the details of the spending policies using the hardware signer's screen is a prerequisite for security in adversarial environments. +Designing a secure protocol for the coordination of a descriptor wallet among distant parties is also a challenging problem that is out of scope in this document. See [[bip-0129.mediawiki|BIP-129 (Bitcoin Secure Multisig Setup)]] for an approach designed for multisignature wallets. Regardless of the approach, the ability for the user to carefully verify all the details of the spending policies using the hardware signer's screen is a prerequisite for security in adversarial environments. === Policy registration as a solution === @@ -136,7 +136,7 @@ A ''wallet descriptor template'' is a <tt>SCRIPT</tt> expression. * ''always'' followed by either: ** the string <tt>/**</tt>, or ** a string of the form <tt>/<NUM;NUM>/*</tt>, for two distinct decimal numbers <tt>NUM</tt> representing unhardened derivations, or -** any of the additional, implementation-specific valid derivation path patterns (see [[#Optional_derivation_paths|Optional derivation paths]] below). +** any of the additional, implementation-specific valid derivation path patterns (see [[#optional-derivation-paths|Optional derivation paths]] below). The <tt>/**</tt> in the placeholder template represents commonly used paths for receive/change addresses, and is equivalent to <tt><0;1>/*</tt>. @@ -294,7 +294,7 @@ Wallet policies are implemented in * the [https://github.com/digitalbitbox/bitbox02-firmware BitBox02 firmware] since version v9.15.0; * [https://github.com/Blockstream/Jade Blockstream Jade] since version v1.0.24, via [https://github.com/ElementsProject/libwally-core libwally-core] v1.0.0. -For development and testing purposes, we provide a [[bip-wallet-policies/wallet_policies.py|Python 3.7 reference implementation]] of simple classes to handle wallet policies, and the conversion to/from output script descriptors. +For development and testing purposes, we provide a [[bip-0388/wallet_policies.py|Python 3.7 reference implementation]] of simple classes to handle wallet policies, and the conversion to/from output script descriptors. The reference implementation is for demonstration purposes only and not to be used in production environments. ==Footnotes== |