From: Jeff Garzik <jgarzik@bitpay.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin address TTL & key expiration?
Date: Tue, 15 Jul 2014 11:55:43 -0400 [thread overview]
Message-ID: <CAJHLa0M9UC+7D+5NK7eHMPMPJb+K-eqpGC77t4ikKLz76GtVPw@mail.gmail.com> (raw)
In-Reply-To: <201407151541.53342.luke@dashjr.org>
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/
next prev parent reply other threads:[~2014-07-15 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 8:00 [Bitcoin-development] Bitcoin address TTL & key expiration? Jeff Garzik
2014-07-15 8:19 ` Wladimir
2014-07-15 8:23 ` Jeff Garzik
2014-07-15 8:31 ` Jeremy Spilman
2014-07-15 8:48 ` Wladimir
2014-07-15 8:20 ` Peter Todd
2014-07-15 10:25 ` Mike Hearn
2014-07-15 14:02 ` Jeff Garzik
2014-07-15 14:27 ` Mike Hearn
2014-07-15 14:48 ` Luke Dashjr
2014-07-15 15:11 ` Jeff Garzik
2014-07-15 15:18 ` Mike Hearn
2014-07-15 15:35 ` Jeff Garzik
2014-07-15 15:41 ` Luke Dashjr
2014-07-15 15:55 ` Jeff Garzik [this message]
2014-07-15 16:26 ` Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJHLa0M9UC+7D+5NK7eHMPMPJb+K-eqpGC77t4ikKLz76GtVPw@mail.gmail.com \
--to=jgarzik@bitpay.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=luke@dashjr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox