<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Dec 3, 2013 at 12:44 AM, Mike Hearn <span dir="ltr"><<a href="mailto:mike@plan99.net" target="_blank">mike@plan99.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">PPv1 doesn't have any notion of fee unfortunately. I suppose it could be added easily, but we also need to launch the existing feature set.</div></blockquote><div><br></div><div>Lets bang out a merchant-pays-fee extension.</div>
<div><br></div><div>How about:</div><div><br></div><div>SPEC:</div><div><br></div><div> optional uint64 allowfee tag number=1000</div><div><br></div><div>Allow up to allowfee satoshis to be deducted from the amount paid to be used to pay Bitcoin network transaction fees. A wallet implementation must not reduce the amount paid for fees more than allowfee, and transaction fees must be equal to or greater than the amount reduced.</div>
<div><br></div><div>:ENDSPEC</div><div><br></div><div>Rationale: we don't want wallet software giving users discounts-- sending transactions that are amount-allowfee without paying any fee. We also want to allow users to pay MORE in fees, if they need to (fragmented wallet, maybe, or big CoinJoin transaction) or decide to.</div>
<div><br></div><div><br></div><div>PS: I think there was also consensus that the BIP72 request=... should be shortened to just r=... (save 6 chars in QR codes). Unless somebody objects, I'll change the BIP and the reference implementation code to make it so...</div>
<div><br></div></div>-- <br>--<br>Gavin Andresen<br>
</div><div class="gmail_extra"><br></div></div>