From: Mike Hearn <mike@plan99•net>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin address TTL & key expiration?
Date: Tue, 15 Jul 2014 16:27:26 +0200 [thread overview]
Message-ID: <CANEZrP1vZ6ZEazViMa3BwBTbu0ihmDJk7ueHUSHJSe9GA9zMhg@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0P97vqzXdk0-P+XEeo1S0xjc-Dsm8K+GjYxGE_O1TmPcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
On Tue, Jul 15, 2014 at 4:02 PM, Jeff Garzik <jgarzik@bitpay•com> wrote:
> BIP70 does not work well for unknown number of future payments of
> unknown, unpredictable value.
You can specify zero as an output value, in which case it's the same as "no
value specified". You can then just reuse the PaymentRequest until it
expires. So I think it provides the same functionality already.
Now sure, you'll get address reuse in this scenario, but that's no worse
than with an extended textual address.
[-- Attachment #2: Type: text/html, Size: 861 bytes --]
next prev parent reply other threads:[~2014-07-15 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 8:00 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 [this message]
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
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=CANEZrP1vZ6ZEazViMa3BwBTbu0ihmDJk7ueHUSHJSe9GA9zMhg@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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