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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1X755P-0001ZH-IK
for bitcoin-development@lists.sourceforge.net;
Tue, 15 Jul 2014 15:56:11 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.50 as permitted sender)
client-ip=74.125.82.50; envelope-from=jgarzik@bitpay.com;
helo=mail-wg0-f50.google.com;
Received: from mail-wg0-f50.google.com ([74.125.82.50])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X755N-0004Jz-In
for bitcoin-development@lists.sourceforge.net;
Tue, 15 Jul 2014 15:56:11 +0000
Received: by mail-wg0-f50.google.com with SMTP id n12so5732851wgh.33
for <bitcoin-development@lists.sourceforge.net>;
Tue, 15 Jul 2014 08:56:03 -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=rbrbya2PI4sxCYf55Ervx+6f/D5g38GZnFOBgKoQfPY=;
b=kX/BL4VF5AAkr55I3R/1Z77CdwjhE3d9S3taWNhb0XVnwUOHR9itWrI86zNtbjN3hp
y0QpAog7GKYUZ49aq9StCnkujsQLf+ZfjCFtyt+NH82fNm4DPKJcENDub46ODdaeO5BU
pOqVjOviv1Li9OlyLKGWyohVCPX095QQNmp6zmCjCR0q+NrxWZf4HSeMZ8Dse2ep32kq
UyJGK8VCz5B6YD2pnTDo+yPRLWBiKLM6SLWFleQHgN0vse+eG7J0sWND3O6UYZ3zy/vq
Hl+7/j2eG1Du67T704J2TvnTW3SN/NeLWX6JE48aGxDlxiyYFpxauQWArK9pXfxj5iwR
C2Mg==
X-Gm-Message-State: ALoCoQmjv1Od72FltdYl61DUGJnVuHM7/E1NkkvOzK0Gz5wa1/babA32Cg7aLviwWbIYp/u8l+Mp
X-Received: by 10.180.24.97 with SMTP id t1mr6643519wif.45.1405439763181; Tue,
15 Jul 2014 08:56:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.5.67 with HTTP; Tue, 15 Jul 2014 08:55:43 -0700 (PDT)
In-Reply-To: <201407151541.53342.luke@dashjr.org>
References: <CAJHLa0M7iEUQnJ9M4A3ev3EQqxUVQG85qucRamvMb0n-CztOFA@mail.gmail.com>
<201407151448.57223.luke@dashjr.org>
<CAJHLa0Nj2f4mSKNggGH4sXZTLYNwdVGO7uMSzN7V_vVKU-6w9Q@mail.gmail.com>
<201407151541.53342.luke@dashjr.org>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, 15 Jul 2014 11:55:43 -0400
Message-ID: <CAJHLa0M9UC+7D+5NK7eHMPMPJb+K-eqpGC77t4ikKLz76GtVPw@mail.gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: text/plain; charset=UTF-8
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: 1X755N-0004Jz-In
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin address TTL & key expiration?
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: Tue, 15 Jul 2014 15:56:11 -0000
On Tue, Jul 15, 2014 at 11:41 AM, Luke Dashjr <luke@dashjr.org> wrote:
> There's no reason deposits cannot use a unique payment request or address
> every time...
Actually, and this is key, there _are_ reasons why deposits might not
be able to use PaymentRequests. Payments happen even when
wallets/computers are offline.
If you have negotiated HD wallet details, you can use a new address
every time, as mentioned.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
