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; 
MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin address TTL & key expiration?
Precedence: list

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/