Timeline for How do deterministic wallets know how many keys to generate?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2017 at 18:12 | comment | added | jiggunjer | Now it makes sense. Thanks. I had a different math definition of deterministic. | |
| Sep 24, 2017 at 17:30 | comment | added | Nick ODell | @jiggunjer It isn't drawn randomly - it's drawn deterministically from a random number. | |
| Sep 24, 2017 at 15:24 | comment | added | jiggunjer | @Nick_Odell how do you know? The generation is a random draw from an infinite set. So I don't see how anyone can guarantee a certain address will be drawn even if you keep drawing 24/7. | |
| Sep 24, 2017 at 14:36 | comment | added | Nick ODell | @jiggunjer No. Set the gap limit high enough, and it will generate every address the client has even shown you, and more. | |
| Sep 24, 2017 at 6:34 | comment | added | jiggunjer | So in theory it in possible an existing address is never generated even at high limits, so even if you knew the exact address you couldn't regenerate the private key? | |
| Apr 13, 2017 at 12:47 | history | edited | CommunityBot |
replaced http://bitcoin.stackexchange.com/ with https://bitcoin.stackexchange.com/
|
|
| Oct 21, 2014 at 5:32 | comment | added | Nate Eldredge | I suppose a full client could handle a much higher gap limit, since it can check the block chain for an address itself, without querying an external server. | |
| Oct 21, 2014 at 5:02 | history | edited | Nick ODell | CC BY-SA 3.0 |
added 244 characters in body
|
| Oct 21, 2014 at 4:54 | history | answered | Nick ODell | CC BY-SA 3.0 |