diff options
| author | Salvatore Ingala <6681844+bigspider@users.noreply.github.com> | 2024-07-27 19:36:08 +0200 |
|---|---|---|
| committer | Salvatore Ingala <6681844+bigspider@users.noreply.github.com> | 2024-07-27 19:36:08 +0200 |
| commit | c2655e0ab988ea2a43264186a368b7b4ec3734f9 (patch) | |
| tree | b5d2c2ef5458bdc46e2dd5579c1a0f51c4a4e496 /bip-0388.mediawiki | |
| parent | 0b3c79c257067dabadb34829fa616534a54f23af (diff) | |
More adjustments from PR review
Diffstat (limited to 'bip-0388.mediawiki')
| -rw-r--r-- | bip-0388.mediawiki | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/bip-0388.mediawiki b/bip-0388.mediawiki index fd28f04..7f0aab5 100644 --- a/bip-0388.mediawiki +++ b/bip-0388.mediawiki @@ -14,7 +14,8 @@ == Abstract == -Software wallets and hardware signing devices sequester wallet uses into logically separate "accounts". +Software wallets and hardware signing devices typically partition funds into separate "accounts". When signing or visualizing transactions, this allows to show to the user aggregate in-flow or out-flow information for one or more involved accounts. + Wallet policies build on top of output script descriptors to represent such accounts in a compact, reviewable way. An account encompasses a logical group of receive and change addresses, and each wallet policy represents all descriptors necessary to describe an account in its entirety. @@ -67,7 +68,7 @@ Reusing keys across different UTXOs harms user privacy by allowing external part By constraining the derivation path patterns to have a uniform structure, wallet policies prevent key reuse among the same or different UTXOs of the same account. -It is strongly recommended to avoid key reuse across accounts. Distinct public keys per account can be guaranteed per hardened derivation paths. This specification does not mandate hardened derivation to maintain compatibility with existing deployments that do not adhere to this recommendation. +It is strongly recommended to avoid key reuse across accounts. Distinct public keys per account can be guaranteed by using distinct hardened derivation paths. This specification does not mandate hardened derivation in order to maintain compatibility with existing deployments that do not adhere to this recommendation. It is out of scope for this document to guarantee that users do not reuse extended public keys among different wallet accounts. This responsibility is left to the users and their software wallet. |