From: Mike Hearn <mike@plan99•net>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Paul Rabahy <prabahy@gmail•com>
Subject: Re: [Bitcoin-development] Merge avoidance and P2P connection encryption
Date: Fri, 13 Dec 2013 09:26:59 -0800 [thread overview]
Message-ID: <CANEZrP1ha6y-w1Cpq+7t1ogUwNmxSobEREY2tawp7bcFGRPKiw@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T0VEu15KXH_XPn+cAERQFz=Tmjqna6ZoNpLrxkzeKw9kQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
>
> Why would there be an iteration count? The payer would handle that,
> wouldn't they?
>
I'm thinking about a use case I hope will become common next year -
pastebin style hosting sites for payment requests. Like, if I as a regular
end user wish to use the payment protocol, I could just upload a (possibly
signed) payment request to:
payr.com/a62gahZ
or whatever, and then payr.com can take care of incrementing the iteration
count on each download of my file. That's why it's useful for it to be
unsigned.
> If the use case is: I give the Foundation a "here's where to pay my
> salary" PaymentRequest, maybe with several Outputs each having a different
> xpubkey, then it seems to me the Foundation's wallet software should take
> care of iterating.
>
Absolutely. The two use cases can both be supported. You could give
iteration ranges, for instance, if you want to specify expiry in terms of
number of payments rather than time.
[-- Attachment #2: Type: text/html, Size: 1749 bytes --]
next prev parent reply other threads:[~2013-12-13 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 16:03 Mike Hearn
2013-12-12 17:28 ` Paul Rabahy
2013-12-12 18:24 ` Mike Hearn
2013-12-13 0:20 ` Gavin Andresen
2013-12-13 0:26 ` Jeff Garzik
2013-12-13 14:43 ` Peter Todd
2013-12-13 17:26 ` Mike Hearn [this message]
2013-12-13 19:19 ` Mark Friedenbach
2013-12-13 21:49 ` 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=CANEZrP1ha6y-w1Cpq+7t1ogUwNmxSobEREY2tawp7bcFGRPKiw@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
--cc=prabahy@gmail$(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