Timeline for How is the association between a seed and its addresses implemented?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 15, 2018 at 19:04 | vote | accept | new_xxx | ||
Feb 15, 2018 at 18:39 | comment | added | new_xxx | By the way, I've also found some answers to questions 2 and 3 here and here. | |
Feb 15, 2018 at 18:31 | comment | added | Zauz | 3. would be a great new question | |
Feb 15, 2018 at 18:30 | comment | added | Zauz | 2. definitely keep track of spent addresses and never use them again (for security reasons) or do something like the current GUI Wallet: never use leading and empty addresses of a seed | |
Feb 15, 2018 at 18:26 | comment | added | Zauz | 1. both have advantages and disadvantages, depends on circumstances and opinion | |
Feb 15, 2018 at 18:12 | comment | added | new_xxx | 3. And why do they say that addresses should be regenerated in a wallet after a snapshot? Isn’t it so that a wallet should constantly have all the required info about its addresses, why does a snapshot require it to take some extra steps to reobtain such info? | |
Feb 15, 2018 at 18:12 | comment | added | new_xxx | 2. Should a wallet store or in some way keep track of all the addresses it has generated? Also, should it mostly ignore the “used” addresses and use only the “active” one(s) in a meaningful way? | |
Feb 15, 2018 at 18:12 | comment | added | new_xxx | 1. In a wallet, should there be the ability to generate a new address at a user's request or should a new address be generated automatically under certain circumstances (e.g., after an old address has been used as the input of some transaction)? | |
Feb 12, 2018 at 22:31 | history | answered | Zauz | CC BY-SA 3.0 |