Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.172 as permitted sender)
	client-ip=74.125.82.172; envelope-from=gavinandresen@gmail.com;
	helo=mail-we0-f172.google.com; 
MIME-Version: 1.0
In-Reply-To: <CANEZrP1PLKemiUEgMJRGdiZXt7o=0_5fhLKYY0x3Ngb_iEm+2w@mail.gmail.com>
References: <CANEZrP3tGdFh6oG5fbX9JbU6sYbbex1cq=0tQB-0A4aDrdbXrQ@mail.gmail.com>
	<l7f97u$jdg$1@ger.gmane.org>
	<5E4597E4-C1C7-4536-8CF0-82EDD7715DAB@plan99.net>
	<l7fpbn$hf6$1@ger.gmane.org>
	<39921E12-B411-4430-9D56-04F53906B109@plan99.net>
	<CAGLkj4C9fyAX1CnB0oZH3BwLRQp6WOo9kLUqDhRUSA6y3LxYvg@mail.gmail.com>
	<CANEZrP1C=Hc-3f-rqQ+wYrPn-eUj52HjN+qRQdJMWvnP+dkK=Q@mail.gmail.com>
	<CAJHLa0P_uzEQ2OG2FTXyD2Zw4RzujNBxKbKD04CSS1sLNpLUUQ@mail.gmail.com>
	<CANEZrP2hf2853w9f4__Ji9v3eRRU0u6pEzPxAmFN+iH067gtnA@mail.gmail.com>
	<CABsx9T3NQDPL6=pz5BD5DsP0qh0x3LJOCj2H3yY5tzL2_DivGA@mail.gmail.com>
	<CANEZrP1PLKemiUEgMJRGdiZXt7o=0_5fhLKYY0x3Ngb_iEm+2w@mail.gmail.com>
Date: Tue, 3 Dec 2013 21:07:30 +1000
Message-ID: <CABsx9T322nCvynRCL6Mb9C0f5EuJSfMDTSGiU+_JsYoSCb=_kQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=001a11c23dc279061d04ec9f4dc5
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Floating fees and SPV clients
Precedence: list

--001a11c23dc279061d04ec9f4dc5
Content-Type: text/plain; charset=ISO-8859-1

Ok, revised spec:

SPEC:

message PaymentDeatils {
    ...
    optional uint64 minfee    tag number=8

Pay at least minfee satoshis in transaction fees. Wallet software should
add minfee to the amount the user authorizes and pays, and include at least
minfee in the transaction created to pay miner's transaction fees. Wallet
software may request that the user pays more, if it must create a complex
transaction or judges that minfee is not sufficient for the transaction to
be accepted by the network..

:ENDSPEC

Making it fee-per-kilobyte is a bad idea, in my opinion; users don't care
how many kilobytes their transactions are, and they will just be confused
if they're paying for a 10mBTC burger and are asked to pay 10.00011 or
9.9994 because the merchant has no idea how many kilobytes the paying
transaction will be.

-- 
--
Gavin Andresen

--001a11c23dc279061d04ec9f4dc5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Ok, revised spec:<div><br></div><div><div style=3D"font-fa=
mily:arial,sans-serif;font-size:13px">SPEC:</div><div style=3D"font-family:=
arial,sans-serif;font-size:13px"><br></div><div style=3D"font-family:arial,=
sans-serif;font-size:13px">
message PaymentDeatils {</div><div style=3D"font-family:arial,sans-serif;fo=
nt-size:13px">=A0 =A0 ...</div><div style=3D"font-family:arial,sans-serif;f=
ont-size:13px">=A0 =A0 optional uint64 minfee =A0 =A0tag number=3D8</div><d=
iv style=3D"font-family:arial,sans-serif;font-size:13px">
<br></div><div style=3D"font-family:arial,sans-serif;font-size:13px">Pay at=
 least minfee satoshis in transaction fees. Wallet software should add minf=
ee to the amount the user authorizes and pays, and include at least minfee =
in the transaction created to pay miner&#39;s transaction fees. Wallet soft=
ware may request that the user pays more, if it must create a complex trans=
action or judges that minfee is not sufficient for the transaction to be ac=
cepted by the network..</div>
<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">:ENDSPEC</div></div><d=
iv><br></div><div>Making it fee-per-kilobyte is a bad idea, in my opinion; =
users don&#39;t care how many kilobytes their transactions are, and they wi=
ll just be confused if they&#39;re paying for a 10mBTC burger and are asked=
 to pay 10.00011 or 9.9994 because the merchant has no idea how many kiloby=
tes the paying transaction will be.</div>
<div class=3D"gmail_extra"><div><br></div>-- <br>--<br>Gavin Andresen<br>
</div></div>

--001a11c23dc279061d04ec9f4dc5--