{ "subject": "Re: Privacy versus Safety: handling change", "content": { "format": "html", "body": "<div class=\"post\">We should queue up a supply of pre-made addresses in the wallet to use when a new address is needed.&nbsp; They aren't very big, so it wouldn't hurt to have a lot of them.&nbsp; This would more generally cover the case also where someone backs up, then requests a new address and receives a big payment with it.&nbsp; Maybe there should be separate queues so one type of demand on addresses doesn't deplete it for the others.<br/><br/>The addresses would be created and stored in the normal place, but also listed on a separate list of created-but-never-used addresses.&nbsp; When an address is requested, the address at the front of the never-used queue is handed out, and a new address is created and added to the back.<br/><br/>There's some kind of rescan in the block loading code that was made to repair the case where someone copied their wallet.dat.&nbsp; I would need to check that the rescan handles the case of rediscovering received payments in blocks that were already received, but are forgotten because the wallet was restored.</div>" }, "source": { "name": "Bitcoin Forum", "url": "https://bitcointalk.org/index.php?topic=434.msg3770#msg3770" }, "date": "2010-07-17T16:27:39Z" }
Inscription number 18,210,178
Genesis block 799,367
File type json
File size 1.35 KB
Creation date