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
|
Return-Path: <mark@friedenbach.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 8354E98A
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Sep 2017 21:09:19 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pg0-f42.google.com (mail-pg0-f42.google.com [74.125.83.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E6954454
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Sep 2017 21:09:18 +0000 (UTC)
Received: by mail-pg0-f42.google.com with SMTP id 188so8445786pgb.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 27 Sep 2017 14:09:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=friedenbach-org.20150623.gappssmtp.com; s=20150623;
h=from:mime-version:subject:date:references:to:in-reply-to:message-id;
bh=9ju0ARzIk5WX9PNbextTa5PJAxYtxI6IHRy4oUzIUa8=;
b=EKEXz4DTtwvhqhvetb+h9oVukvCKYTslXeIouCTLM74xiyneYNERscHG5dfXwwjPFk
6HPHpBSczWzYSqmIPaJswZ9jjK7t4+gXLJHYhiqpfMH3mHsncqdMV6rpqXh1HNnRwYZD
7maWMm6pJj+QfoZPR5KpXvRqmLLW/+vRvJ0uniyKqMrzvQyIvhzwqYlot1wxRn+YixeX
dSQIbkAfKTncZ8GAClv7S68FgUMrMsMxIrnXbgX3jg/axfmdnCV1Zaov43RB/bM7Kues
tYm5roAA2ZFAP0kyr7gsRtb1K3Z0jvowgFnCuUvonWj2WixHZU64MZnkMKVvr2ynYzVP
eIrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:mime-version:subject:date:references:to
:in-reply-to:message-id;
bh=9ju0ARzIk5WX9PNbextTa5PJAxYtxI6IHRy4oUzIUa8=;
b=ehCDVUm7kYDFFyLpm0Yvir7hZiHjHozMDRMS6I7gebogSKsvnabPy8kwkeK2FnIiFp
TnBO4dvftTZZzGEE7iKlbgfY8ByisPWS33v9Zh3GdNtlYbUCz7pt2mjL565hoScKdsNs
5Bw/5sTTPwTzcgkl7CyD9RskVt8gHfTtwv/NEJjvCJRUXcCaNDTo2J/hcvebw+RdxyBy
YYdH+omvxTyDp/hlyhGavRV85eWn4JyA1EIsWvTBXMtKfxAoB9yAlA9NE5lvFejrlUYD
RQ2jyMEO2RUzSS+d5Zr9ekmqu4fL/cGk8G5o08bAUOgMpJoEkhAYKGJCLFxhiwCJHiDT
lhag==
X-Gm-Message-State: AHPjjUjIyHEI/Ul2AQXQZD1A/f/Kf7SPjsALAnqevyWzQ0fYJ/NpauRs
t8H3frHc6tLj6wXAWkueKMkLIyQcuLc=
X-Google-Smtp-Source: AOwi7QAkPRVp0WpCtWfHnp6pccOhRPegjhS6TC//o+N4rhIDgvXS3GPW3UQja4LrMi2rCeVZHeccgw==
X-Received: by 10.84.212.2 with SMTP id d2mr2212594pli.412.1506546558416;
Wed, 27 Sep 2017 14:09:18 -0700 (PDT)
Received: from [10.228.195.77] ([73.93.152.253])
by smtp.gmail.com with ESMTPSA id
n83sm21423171pfi.163.2017.09.27.14.09.17
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 27 Sep 2017 14:09:17 -0700 (PDT)
From: Mark Friedenbach <mark@friedenbach.org>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_ADB2D486-CE96-45BA-8316-9063939B1F88"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 27 Sep 2017 14:09:16 -0700
References: <20170927160654.GA12492@savin.petertodd.org>
<CAAcC9yvdw4Yphs-prpckaouzaU21D=kGRqK+gG9SbPr-=27z9w@mail.gmail.com>
<CY4PR12MB139977628660D809B611D8ACC8780@CY4PR12MB1399.namprd12.prod.outlook.com>
To: Nick Pudar <nick@pudar.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <CY4PR12MB139977628660D809B611D8ACC8780@CY4PR12MB1399.namprd12.prod.outlook.com>
Message-Id: <F2378ADB-C2FB-4253-A7D7-3B52318FA251@friedenbach.org>
X-Mailer: Apple Mail (2.3273)
X-Spam-Status: No, score=0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
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: Thu, 28 Sep 2017 12:51:39 +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 21:09:19 -0000
--Apple-Mail=_ADB2D486-CE96-45BA-8316-9063939B1F88
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
First, there=E2=80=99s been no discussion so far for address expiration =
to be part of =E2=80=9Cthe protocol=E2=80=9D which usually means =
consensus rules or p2p. This is purely about wallets and wallet =
information exchange protocols.
There=E2=80=99s no way for the sender to know whether an address has =
been used without a complete copy of the block chain and more indexes =
than even Bitcoin Core maintains. It=E2=80=99s simply not an option now, =
let alone as the blockchain grows into the future.
> On Sep 27, 2017, at 1:23 PM, Nick Pudar via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> As a long term silent reader of this list, I felt compelled to comment =
on this address expiration topic. I don't believe that address =
expiration should be part of the protocol. I think instead that the =
"sending" feature should by default offer guidance to request a fresh =
address from the recipient. Also allow the receiver of funds to be able =
to generate an "invoice" that the sender acts on.
>=20
> I also think that re-directs are fraught with privacy issues. At the =
end of the day, the ultimate burden is on the sender (with much self =
interest from the receiver) that the correct address is being used.
--Apple-Mail=_ADB2D486-CE96-45BA-8316-9063939B1F88
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">First, there=E2=80=99s been no discussion so =
far for address expiration to be part of =E2=80=9Cthe protocol=E2=80=9D =
which usually means consensus rules or p2p. This is purely about wallets =
and wallet information exchange protocols.</div><div class=3D""><br =
class=3D""></div><div class=3D"">There=E2=80=99s no way for the sender =
to know whether an address has been used without a complete copy of the =
block chain and more indexes than even Bitcoin Core maintains. It=E2=80=99=
s simply not an option now, let alone as the blockchain grows into the =
future.</div><br class=3D""><div><blockquote type=3D"cite" class=3D""><div=
class=3D"">On Sep 27, 2017, at 1:23 PM, Nick Pudar via bitcoin-dev =
<<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" =
class=3D"">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
id=3D"divtagdefaultwrapper" dir=3D"ltr" style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: =
12pt; font-family: Calibri, Helvetica, sans-serif, EmojiFont, 'Apple =
Color Emoji', 'Segoe UI Emoji', NotoColorEmoji, 'Segoe UI Symbol', =
'Android Emoji', EmojiSymbols;" class=3D""><div style=3D"margin-top: =
0px; margin-bottom: 0px;" class=3D"">As a long term silent reader of =
this list, I felt compelled to comment on this address expiration =
topic. I don't believe that address expiration should be part of =
the protocol. I think instead that the "sending" feature should by =
default offer guidance to request a fresh address from the =
recipient. Also allow the receiver of funds to be able to generate =
an "invoice" that the sender acts on.<br class=3D""></div><div =
style=3D"margin-top: 0px; margin-bottom: 0px;" class=3D""><br =
class=3D""></div><div style=3D"margin-top: 0px; margin-bottom: 0px;" =
class=3D"">I also think that re-directs are fraught with privacy =
issues. At the end of the day, the ultimate burden is on the =
sender (with much self interest from the receiver) that the correct =
address is being used.</div></div></div></blockquote></div><br =
class=3D""></body></html>=
--Apple-Mail=_ADB2D486-CE96-45BA-8316-9063939B1F88--
|
