📅 Original date posted:2017-09-27
📝 Original message:See https://github.com/bitcoin/bitcoin/pull/9722
What still needs to be done is that during the first start up after
updating with this popup, the wallet needs to scan for addresses that
have been used in the past. That way the popup isn't only shown for
addresses that are reused after updating.
On 09/27/2017 12:35 PM, Chris Priest via bitcoin-dev wrote:
> A better solution is to just have the sending wallet check to see if
> the address you are about to send to has been used before. If it's a
> fresh address, it sends it through without any popup alert. If the
> address has history going back a certain amount of time, then a popup
> comes up and notifies the sender that they are sending to a non-fresh
> address that may no longer be controlled by the receiver anymore.
>
> Also, an even better idea is to set up an "address expiration
> service". When you delete a wallet, you first send off an "expiration
> notice" which is just a message (signed with the private key) saying
> "I am about to delete this address, here is my new address". When
> someone tries to send to that address, they first consult the address
> expiration service, and the service will either tell them "this
> address is not expired, proceed", or "this address has been expired,
> please send to this other address instead...". Basically like a 301
> redirect, but for addresses. I don't think address expiration should
> be part of the protocol.
>
...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170927/305de41f/attachment-0001.html>;
CryptAxe [ARCHIVE] /
npub12p…js309
2023-06-07 18:06:21
in reply to nevent1q…wflz
Author Public Key
npub12p7jzesdg8kxdg8rujr20znnd868fgugczkwh4cyxwa6gnxj5sxsnjs309Published at
2023-06-07 18:06:21Event JSON
{
"id": "17f240d976d1586e5202bdee58b8eeebf114ea0121a0c207b8ebdcac73c376d5",
"pubkey": "507d21660d41ec66a0e3e486a78a7369f474a388c0acebd70433bba44cd2a40d",
"created_at": 1686161181,
"kind": 1,
"tags": [
[
"e",
"02d8c76b933e43bf4fbef62deb34ae55389c59e653682f6f8847f8910b9dcb32",
"",
"root"
],
[
"e",
"5b67390b62748f1103e09c1556778b24713cd41c6f72e02381634715907c5063",
"",
"reply"
],
[
"p",
"3b5311200328974edeaa105b1a8f60d243e653cc63b6bb29f61dc696e04189ed"
]
],
"content": "📅 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",
"sig": "b84f87b871d277461d56b3eaf4c141b2281c71142efc490bb02223b424b03a2ca1e540a7c5f2e2dc86c10b5bd6025c1baea4beb1f1ec26d0175c12b0776466d8"
}