mirror of
https://github.com/bitcoin/bips.git
synced 2025-06-30 12:42:43 +00:00
remove bip44 stuff
This commit is contained in:
parent
3664283eb4
commit
38096cedd9
@ -111,35 +111,6 @@ This number is used as child index in BIP32 derivation.
|
|||||||
|
|
||||||
Public derivation is used at this level.
|
Public derivation is used at this level.
|
||||||
|
|
||||||
==Account discovery==
|
|
||||||
|
|
||||||
When the master seed is imported from an external source the software should
|
|
||||||
start to discover the accounts in the following manner:
|
|
||||||
|
|
||||||
* derive the first accounts node (index = 0)
|
|
||||||
* derive the external chain node of this account
|
|
||||||
* scan addresses of the external chain; respect the gap limit described below
|
|
||||||
* if no transactions are found on the external chain, stop discovery
|
|
||||||
* if there are some transactions, increase the account index and go to step 1
|
|
||||||
|
|
||||||
This algorithm is successful because software should disallow creation of new
|
|
||||||
accounts if previous one has no transaction history, as described in chapter
|
|
||||||
"Account" above.
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
===Address gap limit===
|
|
||||||
|
|
||||||
Address gap limit is currently set to 20. If the software hits 20 unused
|
|
||||||
addresses in a row, it expects there are no used addresses beyond this point
|
|
||||||
and stops searching the address chain. We scan just the external chains, because
|
|
||||||
internal chains receive only coins that come from the associated external chains.
|
|
||||||
|
|
||||||
Wallet software should warn when the user is trying to exceed the gap limit on
|
|
||||||
an external chain by generating a new address.
|
|
||||||
|
|
||||||
==Examples==
|
==Examples==
|
||||||
|
|
||||||
{|
|
{|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user