summaryrefslogtreecommitdiff
path: root/f0/536fd195494824fe63719988fd236998aaf274
blob: e594ca6467229df2b054c30c66fd76aad1f363b1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
Return-Path: <cryptaxe@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id A9532A7A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 27 Sep 2017 20:19:21 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pf0-f173.google.com (mail-pf0-f173.google.com
	[209.85.192.173])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3A1C94CF
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 27 Sep 2017 20:19:21 +0000 (UTC)
Received: by mail-pf0-f173.google.com with SMTP id e1so7815113pfk.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 27 Sep 2017 13:19:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=subject:to:references:from:message-id:date:user-agent:mime-version
	:in-reply-to:content-language;
	bh=toJgy6RT/w55ap0J6dbqBAeEY95tNlo529S+JGzXBT8=;
	b=kuhRZ3WVFokFrD5wunN67cU0da7DWVgH6x30mGpPlM8hG7Oqel+ZQcCmD8Lh7QhQQW
	OdD5MeldwQEiTAIDeNywbvfFLw7wu1F0hpqL3uwDnG1c3uUgGjcvlkyO3TM/PyZTp9fJ
	mnzWhTF9QxUQ0hMGxa0iou3geV460zn8YiiJO4VXsn8NVrwjo7LsVDqXmE9sm/VOA2Wq
	l0sOfVKelwUpYQQdrODi1Ls8uUt3pBk2sJl32hZGSvARWwUKa7cy4hhw5Xkgp3tIBZ24
	0bW4IADD+kAwSq3Ywfsv/WXyGR74gJ+y7hzVfCOyHifDGUJBxauzlwsI2KBS+79M6PHd
	8Yvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-language;
	bh=toJgy6RT/w55ap0J6dbqBAeEY95tNlo529S+JGzXBT8=;
	b=qHht0c/zKqUdkPoRyJTYTc91+Y1D0Z/apmdlYAnZjzN6ouJqAcnG+Ht6f/R0PM1NcD
	MveGQxm5I/BoENhPP6QZnnyeNQqZulWh8E3ikAUmZOoGdyq+LfBl9iUypSibJ8SagKSL
	kg1MVFXGS7+losRGI8VcnG9iG1hpPRa0YVO8Gs62JT24TN2bOSeWHryZLVQXXlB8dqO1
	PfA03Zv76V2Y5SE/mbdvuJNaOyPHcaAPYBnJEUjslgzc3HrbJ67TYGc8U9LTFBd+EGsa
	hEOW+t+SiuYIVeWeMG0Q4qcvzuK5o53kxElEz8BjPvcrMVDrx9rM4/lVoTtSMhsXx5Pu
	LU3w==
X-Gm-Message-State: AHPjjUjqKsUVpFRy5FwgSwOa0W48KSSqbl1CQWarRALLIehT50hPzePJ
	Gvfm00jIhvxuCGYLmwqw5oCtWfCw
X-Google-Smtp-Source: AOwi7QBE4B9LfMcqcwNw3ojr+67EV2AQRwuMg36G68XPkpBtNaw3EwWZK1MYA2yXs/1xnZ0PKSs4gw==
X-Received: by 10.84.224.75 with SMTP id a11mr2163738plt.106.1506543560322;
	Wed, 27 Sep 2017 13:19:20 -0700 (PDT)
Received: from [192.168.1.3] (c-73-240-125-172.hsd1.or.comcast.net.
	[73.240.125.172]) by smtp.gmail.com with ESMTPSA id
	p124sm7982587pfg.179.2017.09.27.13.19.18
	for <bitcoin-dev@lists.linuxfoundation.org>
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Wed, 27 Sep 2017 13:19:19 -0700 (PDT)
To: bitcoin-dev@lists.linuxfoundation.org
References: <20170927160654.GA12492@savin.petertodd.org>
	<CAAcC9yvdw4Yphs-prpckaouzaU21D=kGRqK+gG9SbPr-=27z9w@mail.gmail.com>
From: CryptAxe <cryptaxe@gmail.com>
Message-ID: <0e625a3c-46fa-239f-e646-cf97ae226df0@gmail.com>
Date: Wed, 27 Sep 2017 13:11:09 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
	Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAAcC9yvdw4Yphs-prpckaouzaU21D=kGRqK+gG9SbPr-=27z9w@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------DDDE22FFC9C6136C54289F11"
Content-Language: en-US
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE
	autolearn=disabled version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 27 Sep 2017 20:21:56 +0000
Subject: Re: [bitcoin-dev] Address expiration times should be added to
	BIP-173
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Sep 2017 20:19:21 -0000

This is a multi-part message in MIME format.
--------------DDDE22FFC9C6136C54289F11
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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.
>
...

--------------DDDE22FFC9C6136C54289F11
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>See <a class="moz-txt-link-freetext" href="https://github.com/bitcoin/bitcoin/pull/9722">https://github.com/bitcoin/bitcoin/pull/9722</a> <br>
    </p>
    <p>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.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 09/27/2017 12:35 PM, Chris Priest
      via bitcoin-dev wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAAcC9yvdw4Yphs-prpckaouzaU21D=kGRqK+gG9SbPr-=27z9w@mail.gmail.com">
      <div dir="ltr">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.
        <div><br>
        </div>
        <div>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.</div>
      </div>
      <div class="gmail_extra"><br>
      </div>
    </blockquote>
    ...<br>
  </body>
</html>

--------------DDDE22FFC9C6136C54289F11--