@ -524,7 +524,7 @@ defining what key derivation path to use. For example, BIP44 defines
`m/44'/0'/0'` as the path to use for keys in P2PKH scripts (a
legacy address). A wallet application implementing this standard uses
the keys in that path both when it is first started and after a
restoration from a recovery code. We call this solution _implicit
restoration from a recovery code. We call((("implicit paths", id="implicit-path"))) this solution _implicit
paths_. Several popular implicit paths defined by BIPs are shown in <<bip_implicit_paths>>
++++
@ -563,7 +563,7 @@ paths_. Several popular implicit paths defined by BIPs are shown in <<bip_implic
++++
The second solution is to back up the path information with the recovery
code, making it clear which path is used with which scripts. We call
code, making it clear which path is used with which scripts. We ((("explicit paths", id="explicit-path")))call
this _explicit paths_.
The advantage of implicit paths is that users don't need to keep a record
@ -652,7 +652,7 @@ single signature scripts to use implicit paths. Wallet applications
designed for multiple signatures or other advanced scripts are
increasingly adopting support for explicit paths using descriptors.
Applications that do both will usually conform to the standards for
implicit paths and also provide ((("wallets", "key generation", "backing up derivation paths", startref="wallet-keygen-backups")))((("key generation", "backing up derivation paths", startref="keygen-backups")))((("backing up", "key derivation paths", startref="backup-key-derive")))descriptors.
implicit paths and also provide ((("wallets", "key generation", "backing up derivation paths", startref="wallet-keygen-backups")))((("key generation", "backing up derivation paths", startref="keygen-backups")))((("backing up", "key derivation paths", startref="backup-key-derive")))((("implicit paths", startref="implicit-path")))((("explicit paths", startref="explicit-path")))descriptors.
clenser
7 months ago