<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div class="im"><span style="color:rgb(34,34,34)">Why would there be an iteration count? The payer would handle that, wouldn't they?</span></div></div></div></div></blockquote><div><br></div><div>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:</div>
<div><br></div><div><a href="http://payr.com/a62gahZ">payr.com/a62gahZ</a></div><div><br></div><div>or whatever, and then <a href="http://payr.com">payr.com</a> 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.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><span style="color:rgb(34,34,34)">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.</span></div>
</div></div></div></blockquote><div><br></div><div>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.</div>
</div></div></div>