diff options
| author | Salvatore Ingala <6681844+bigspider@users.noreply.github.com> | 2024-08-14 15:07:55 +0200 |
|---|---|---|
| committer | Salvatore Ingala <6681844+bigspider@users.noreply.github.com> | 2024-08-14 15:07:55 +0200 |
| commit | 1811613e07f878a42ebeb57e714cdc93664082d3 (patch) | |
| tree | 9f75d69a52464a612b1d2e5f4b2a47c409c2f277 | |
| parent | 00fbea5dcd5e90449f270a046ac3fcfdea100b65 (diff) | |
Further improvements from PR review
| -rw-r--r-- | bip-0388.mediawiki | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0388.mediawiki b/bip-0388.mediawiki index 6524441..895e5a0 100644 --- a/bip-0388.mediawiki +++ b/bip-0388.mediawiki @@ -14,7 +14,7 @@ == Abstract == -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. +Software wallets and hardware signing devices typically partition funds into separate "accounts". When signing or visualizing a transaction, aggregate flows of funds of all accounts affected by the transaction may (and should) be displayed to the user. 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. @@ -70,7 +70,7 @@ By constraining the derivation path patterns to have a uniform structure, wallet 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. +It is out of scope for this document to guarantee that users do not reuse extended public keys among different wallet accounts. This is still very important, but the responsibility is left to the users and their software wallet. ==== UX issues ==== |