You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Derive the wallet's first account's node (index = 0)
131
131
# Derive the external chain node of this account (index = 0)
132
132
# Scan addresses of the external chain; respect the gap limit described below
133
-
# If there are some transactions, increase the account index and go to step 2
134
-
# 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.
133
+
# If there are some transactions, increase the account index and go to Step 2
134
+
# 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.
135
135
136
-
Please note that the algorithm works with the transaction history, not account
137
-
balances, so you can have an account with 0 total coins and the algorithm will
138
-
still continue with discovery.
136
+
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.
139
137
140
138
The wallet implementation should scan the accounts and addresses following the parent descriptor string.
141
139
@@ -147,7 +145,7 @@ Wallet software should warn when the user is trying to exceed the gap limit on a
147
145
148
146
===Account Gap Limit===
149
147
150
-
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.
148
+
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.
0 commit comments