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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1W3ZYd-0002Ys-Fc
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Jan 2014 23:07:35 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.179 as permitted sender)
client-ip=209.85.212.179; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f179.google.com;
Received: from mail-wi0-f179.google.com ([209.85.212.179])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W3ZYc-0006VW-I0
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Jan 2014 23:07:35 +0000
Received: by mail-wi0-f179.google.com with SMTP id hr1so2912227wib.12
for <bitcoin-development@lists.sourceforge.net>;
Wed, 15 Jan 2014 15:07:28 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=3xluf5BkeMjvYcw/tUkpkyYRpU0zOpcGedekJtxp6CI=;
b=UvSNJGYYtKf3vICcTkGtcLX2RdiIZoIY4Vg3oENzg2ru6qHEPmUfnlKzI3/k75C3E+
mGdc+zgjrj04uqCvoW4LmGTi37OSvnGr4YcwbVfMJvEcDJOHd3HJH+JP+BnNs0ned1BF
m6lWC0LIoLNnxBFeXOq6JjuMOsAIyKHKvq7A64K+U6FxncgW9a+49CoDxfwZbVFEh9lb
qf4aKnIF0PsUPtUQ1g2NV9k7cBfSl9GWruEsmYvyOcpBawiiW63VKJRs3q0Qbs0DierD
H4INaHkda1LLF1YT3qy5+3fwlIcgOw1AnHk+Its//HsOBd5RoDKTG42fo3OmaHYg6ymG
Lg+g==
X-Gm-Message-State: ALoCoQnx/yLFHfmtqDOWLrJ2NZ/dVnOnLtmfo6MU+MTjbQbe7DgIgpRUHL2PvC//7a7PpBJMhS65
MIME-Version: 1.0
X-Received: by 10.180.79.106 with SMTP id i10mr4742437wix.23.1389827248293;
Wed, 15 Jan 2014 15:07:28 -0800 (PST)
Received: by 10.194.2.164 with HTTP; Wed, 15 Jan 2014 15:07:28 -0800 (PST)
In-Reply-To: <20140115230423.GU38964@giles.gnomon.org.uk>
References: <CABsx9T2G=yqSUGr0+Ju5-z9P++uS20AwLC+c3DnFMHtcQjQK6w@mail.gmail.com>
<CAAS2fgTz0TaGhym_35V3N2-vHVzU9BeuV8q+QJjwh5bg77FEZg@mail.gmail.com>
<CANEZrP0huBWqgvQik9Yc26Tu4CwR0VSXcfC+qfzsZqvoU4VJGA@mail.gmail.com>
<20140113133746.GI38964@giles.gnomon.org.uk>
<CANEZrP1KAVhi_-cxCYe0rR9LUSYJ8MyW8=6eSJZ65FeY5ZJNuQ@mail.gmail.com>
<20140114225321.GT38964@giles.gnomon.org.uk>
<CANAnSg0tH_bK_19rsRRHOeZgrGYeWMhW89fXPyS4DQGmS4r_7A@mail.gmail.com>
<CALimQCXgc0eXeOcqFGUaCpSF7gKEe87KzvLqHZwUysV3WyjjGw@mail.gmail.com>
<CAAS2fgShChAQryfUOBp60jB-zxn2tH986fu1HfT+LsNdBYnoYg@mail.gmail.com>
<CAJHLa0P5r2+kxy7w8G=h=TAhdk1jUoW5UOiv-euo47uQY0u9ZA@mail.gmail.com>
<20140115230423.GU38964@giles.gnomon.org.uk>
Date: Wed, 15 Jan 2014 18:07:28 -0500
Message-ID: <CAJHLa0PeYFNQS3iw-GVG5pU8P2eeuk5k0x7fQHtb4m6SEfzZ7w@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Roy Badami <roy@gnomon.org.uk>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1W3ZYc-0006VW-I0
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Stealth Addresses
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: Wed, 15 Jan 2014 23:07:35 -0000
"Routing address" is pretty good too. Unsure whether the synergy and
familiarity with bank routing numbers improves the situation, or
not...
On Wed, Jan 15, 2014 at 6:04 PM, Roy Badami <roy@gnomon.org.uk> wrote:
> On Wed, Jan 15, 2014 at 03:44:17PM -0500, Jeff Garzik wrote:
>> "static address" seems like a reasonable attempt at describing intended
>> use/direction.
>
> ...as opposed to an address configured by DHCP?
>
> More seriously, I don't think a typical user will understand anything from
> the phrase "static address". But it is a neutral name, and it is shorter
> than "address-of-a-type-for-which-reuse-is-not-deprecated". :-)
>
> -roy
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
