diff options
| author | Robert Spigler <RobertSpigler@ProtonMail.ch> | 2021-03-22 01:27:52 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-22 01:27:52 -0400 |
| commit | 453d3282659e7fab9fbcfab9e8c09b0c16c861d4 (patch) | |
| tree | 8eaed105bf84c81016023c8c83fd254c26b29ac1 | |
| parent | 1361af2f731703e5c6e195d82d8b32de5fb0c593 (diff) | |
| download | bips-453d3282659e7fab9fbcfab9e8c09b0c16c861d4.tar.xz | |
Grammar/formatting
| -rw-r--r-- | Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki b/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki index 68eeae0..b0c8f26 100644 --- a/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki +++ b/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki @@ -124,18 +124,16 @@ Public derivation is used at this level. ==Address Discovery== -The multisig descriptor that is generated from the cosigners combined key records should be used to generate and discover addresses. For example: +The multisig descriptor that is generated from the cosigners' combined key records should be used to generate and discover addresses. For example: <code>wsh(sortedmulti(2,[xfpForA/XY'/0'/0']XpubA/*,[xfpForB/XY'/0'/0']XpubB/*))#Checksum</code> # Derive the wallet's first account's node (index = 0) # Derive the external chain node of this account (index = 0) # Scan addresses of the external chain; respect the gap limit described below -# If there are some transactions, increase the account index and go to step 2 -# If no transactions are found on the external chain, continue to search the following account indexes in compliance with the account gap limit described below. +# If there are some transactions, increase the account index and go to Step 2 +# If no transactions are found on the external chain, continue to search the following account indices in compliance with the account gap limit described below. -Please note that the algorithm works with the transaction history, not account -balances, so you can have an account with 0 total coins and the algorithm will -still continue with discovery. +Please note that the algorithm works with the transaction history, not account balances, so you can have an account with 0 total coins and the algorithm will still continue with discovery. The wallet implementation should scan the accounts and addresses following the parent descriptor string. @@ -147,7 +145,7 @@ Wallet software should warn when the user is trying to exceed the gap limit on a ===Account Gap Limit=== -Account gap limit is currently set to 5. When the software hits an account that contains 20 unused addresses in a row, it will search the the next 4 accounts (while obeying the address gap limit), before stoping discovery. If any transactions are found during this process, discovery is restarted (after finding 20 unused addresses) on the next account index, and the account gap limit is reset. Only when the address gap limit is found consecutively for the account gap limit is discovery stopped. +Account gap limit is currently set to 5. When the software hits an account that contains 20 unused addresses in a row, it will search the next 4 accounts (while obeying the address gap limit), before stopping discovery. If any transactions are found during this process, discovery is restarted (after finding 20 unused addresses) on the next account index, and the account gap limit is reset. Only when the address gap limit is found consecutively for the account gap limit is discovery stopped. ==Rationale== |