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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@monetize.io>) id 1Vh64a-0000aR-V2
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Nov 2013 23:11:41 +0000
Received: from mail-ob0-f182.google.com ([209.85.214.182])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vh64V-0002hz-1x
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Nov 2013 23:11:40 +0000
Received: by mail-ob0-f182.google.com with SMTP id wp18so2982019obc.41
for <bitcoin-development@lists.sourceforge.net>;
Thu, 14 Nov 2013 15:11:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:organization:user-agent
:mime-version:to:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=MQLS/dj9TTG49FU4WwRTrPSN4uDXTL5/yB79aS2QUAs=;
b=Fob18fvlkDkOT1Ecwz+0p0EH4J/m3wAui9kEcfvmpbCapqbJkJfufWj9TT1Cxn8FsR
l3kVWDOtZtDzqbdXseZvZZXJhtJGlSYD2ikvdcwvh/uLK8CcNbuBrR6YE54gDeRQsq9S
osHSSGdEjRj924nflbS7g+/KoCehpjvvRiLzNJj7XTyojLADby3/ERrdpfvzFhjc4Zq5
+6XyxbR8QSqmUhPLLf4PlmEad9BZSYIpw1vcYZemZO4p/NxD3B8xag8q1XAoUQnks/4I
fU/eDTZLygzpxo6fB+QwEah9kpr+zOrUPb3HAlVDOjRHbI0+DvBprfSqU+aGVU/+xJEC
NPGA==
X-Gm-Message-State: ALoCoQm1Lby5uQDjZW+1qR6cSWWcq1k4ThJ7ntCLrFoaUoni0RNnWyzxIhpYsmojvOkumpYhvlmC
X-Received: by 10.182.191.36 with SMTP id gv4mr3837199obc.103.1384470689449;
Thu, 14 Nov 2013 15:11:29 -0800 (PST)
Received: from [192.168.1.118] (adsl-71-131-180-41.dsl.sntc01.pacbell.net.
[71.131.180.41])
by mx.google.com with ESMTPSA id eg8sm219292obd.6.2013.11.14.15.11.28
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 14 Nov 2013 15:11:28 -0800 (PST)
Message-ID: <5285589E.10707@monetize.io>
Date: Thu, 14 Nov 2013 15:11:26 -0800
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAKaEYhK4oXH3hB7uS3=AEkA6r0VB5OYyTua+LOP18rq+rYajHg@mail.gmail.com> <528547FD.2070300@gmail.com> <CAJfRnm7-34jwX0m+0Trj9-YvXFeUYMGq35AoRkY7bq9w-XpabA@mail.gmail.com>
<201311142301.39550.luke@dashjr.org>
In-Reply-To: <201311142301.39550.luke@dashjr.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: enigmail.net]
0.0 T_FILL_THIS_FORM_SHORT Fill in a short form with personal
information
X-Headers-End: 1Vh64V-0002hz-1x
Subject: Re: [Bitcoin-development] moving the default display to mbtc
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 14 Nov 2013 23:11:41 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/14/13 3:01 PM, Luke-Jr wrote:
> I think we all know the problems with the term "address". People
> naturally compare it to postal addresses, email addresses, etc,
> which operate fundamentally different. I suggest that we switch to
> using "invoice id" to refer to what is now known as addresses, as
> that seems to get the more natural understanding to people. On the
> other hand, with the advent of the payment protocol, perhaps
> address/invoice id use will die out soon?
>
> Thoughts?
"key id" (thanks sipa).
I know it's a more technical term, but that is rather the point. It
was a fundamental error to call hashed-pubkeys "addresses" as people
either associate this with "account" or physical addresses, which also
rarely change.
Security and privacy guarantees of the system are defeated when key
pairs are reused. We should ideally adopt terminology that lead people
to associations of ephemeral, temporary use. "key id" is at least
neutral in this regard. Can anyone think of something better?
Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJShVieAAoJEAdzVfsmodw4TlkP/i2cZm9NolReIsv6WBNQUGZ6
0VJveOcsOmEXj3ixSyzPRitFl52EOfU+LZaM3liwFPczuIOXZUXOLAJqakxGGsFa
cWwvZjrBk13aTR+4dXZ6OWcCNmTfm6+st2+v1MpQcXlHD8J1WtrdrzKr3fNSntir
yHbNmF6hPfgLr64m52BhUVrxBg9eiIFDI6VCzmUgk+paNmIxs9dgx7POnz1/hQb3
2FGfNt2J81t4F78mpzjtKx+vHRyHpIKJ2+3mjzcQ7IBkhBgPYnp69TwBSGXbg7l9
6yV0P7DGjWepO5+s96GCjbScYpmZO0gx0ZTn/eamfxh20XuX2fZBEVNd1KnhX4Xq
D4UwylGNa5FteRgURtVN5Xdb82jB2qhhr/IkGSgKds24zhHzgvBgvLJBgwtQHwil
M/y2DMC70WVEXf0Fz96L1kNYUA6062/ZNlwITRWxkUUJprF+xyN3R+BVWMggBMnR
Vjht74MZMkJyYlPQr8BRbYdhgMwv6dh0v5T4M6ck6MjKYj/GLsnEfHyY2d/BNg8c
2nkcBC8Dtv9KoFOk6STS1n7R4ooqepmdsRNPBZUzKvv/NN1B1A8jeluLiN9hSzl1
ubDF/34LJTji8bP9jfDBEND94xdaKjTl+2ISweRttBOOVqCtQlzCQ4udiT7vAntb
AYYMBYmYO/A926T+K6Lp
=kFj9
-----END PGP SIGNATURE-----
|
