{"type":"rich","version":"1.0","author_name":"npub12p7jzesdg8kxdg8rujr20znnd868fgugczkwh4cyxwa6gnxj5sxsnjs309","author_url":"https://nostr.ae/npub12p7jzesdg8kxdg8rujr20znnd868fgugczkwh4cyxwa6gnxj5sxsnjs309","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-09-27\n📝 Original message:See https://github.com/bitcoin/bitcoin/pull/9722\n\nWhat still needs to be done is that during the first start up after\nupdating with this popup, the wallet needs to scan for addresses that\nhave been used in the past. That way the popup isn't only shown for\naddresses that are reused after updating.\n\n\nOn 09/27/2017 12:35 PM, Chris Priest via bitcoin-dev wrote:\n\u003e A better solution is to just have the sending wallet check to see if\n\u003e the address you are about to send to has been used before. If it's a\n\u003e fresh address, it sends it through without any popup alert. If the\n\u003e address has history going back a certain amount of time, then a popup\n\u003e comes up and notifies the sender that they are sending to a non-fresh\n\u003e address that may no longer be controlled by the receiver anymore.\n\u003e\n\u003e Also, an even better idea is to set up an \"address expiration\n\u003e service\". When you delete a wallet, you first send off an \"expiration\n\u003e notice\" which is just a message (signed with the private key) saying\n\u003e \"I am about to delete this address, here is my new address\". When\n\u003e someone tries to send to that address, they first consult the address\n\u003e expiration service, and the service will either tell them \"this\n\u003e address is not expired, proceed\", or \"this address has been expired,\n\u003e please send to this other address instead...\". Basically like a 301\n\u003e redirect, but for addresses. I don't think address expiration should\n\u003e be part of the protocol.\n\u003e\n...\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170927/305de41f/attachment-0001.html\u003e"}
