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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1Wb9kd-0001Tr-Km
for bitcoin-development@lists.sourceforge.net;
Fri, 18 Apr 2014 14:26:47 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.169 as permitted sender)
client-ip=209.85.212.169; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f169.google.com;
Received: from mail-wi0-f169.google.com ([209.85.212.169])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wb9ka-0005CT-7u
for bitcoin-development@lists.sourceforge.net;
Fri, 18 Apr 2014 14:26:47 +0000
Received: by mail-wi0-f169.google.com with SMTP id hm4so1105990wib.4
for <bitcoin-development@lists.sourceforge.net>;
Fri, 18 Apr 2014 07:26:38 -0700 (PDT)
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:from:date
:message-id:subject:to:cc:content-type;
bh=V52RgCKPCXoQnoFJZP5sqJQRrvfUVviVABfTqDBr2kk=;
b=DQyb1W31w8DKyIxrd1FBMwLo0g7s+/O7uRSxl35SDGvEaeOprLPUw+3BhfY67ee4HZ
DDWGHGfYWgALcrM+T1qPS3ArVS/bFoX7ASrob3ZjHl5TNkE4Q8bIqj5nHW1O/CdXzLX4
j64GWjHlAflxsdKb2b2wBCJAo0ygo8UjHQ7E3hEn+PvnCR9u9y4+WaabiFin50w9MGCX
9S4jNFGB0N1BiVD4dgr+kUnlyI72vT40g6EW5litagOlBdbqBRwLwfNRFSAY6jL0xpcm
sfXWQ0YVXbx7CNHPIQGBp1UbxtNM7f4aRDlpU7KZFJ013PMZofiRMxNnLbQtq06QO3EV
7v2Q==
X-Gm-Message-State: ALoCoQmSr0QH3uwAYHOuRqikZ4K2BfltvxTG13jJQSVMTZnScrar/F+/pq3SR+bv8t/yPAnTmb7r
X-Received: by 10.194.118.163 with SMTP id kn3mr820505wjb.77.1397831198026;
Fri, 18 Apr 2014 07:26:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.243.138 with HTTP; Fri, 18 Apr 2014 07:26:17 -0700 (PDT)
In-Reply-To: <20140416110627.GA8131@netbook.cypherspace.org>
References: <CA+s+GJDdENtqQt1f+L5htuuyPxUxsq0prLQFBLirTjJz0nG1gw@mail.gmail.com>
<CAKaEYhKDDCSOiygnfsMpO-dQKjwHnm0icoH9+oGqo+114_9sAQ@mail.gmail.com>
<CA+s+GJB6aThjpMOUodK2Uc-jw=x6rSuRyX5gqsS+mK=DxJ7N5g@mail.gmail.com>
<20140416110627.GA8131@netbook.cypherspace.org>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 18 Apr 2014 10:26:17 -0400
Message-ID: <CAJHLa0Pzazg2zXGA3ZBDg3GLgoGYhP6uzy804u69s+sR3w7vMA@mail.gmail.com>
To: Adam Back <adam@cypherspace.org>
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: 1Wb9ka-0005CT-7u
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] mid-term bitcoin security (Re: Warning
message when running wallet in Windows XP (or drop support?))
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: Fri, 18 Apr 2014 14:26:47 -0000
On Wed, Apr 16, 2014 at 7:06 AM, Adam Back <adam@cypherspace.org> wrote:
> Btw not to reignite the stealth vs reusable address bike shedding, but
> contrarily I was thinking it maybe actually better to try to rebrand address
> as "invoice number". People understand double paying an invoice is not a
> good idea. And if they receive the same invoice twice they'll query it.
And that is certainly how BitPay works today, including the language used.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
