1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1VnnpJ-0003yB-Pm
for bitcoin-development@lists.sourceforge.net;
Tue, 03 Dec 2013 11:07:37 +0000
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;
Received: from mail-we0-f172.google.com ([74.125.82.172])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VnnpI-0004e7-UB
for bitcoin-development@lists.sourceforge.net;
Tue, 03 Dec 2013 11:07:37 +0000
Received: by mail-we0-f172.google.com with SMTP id w62so7727680wes.31
for <bitcoin-development@lists.sourceforge.net>;
Tue, 03 Dec 2013 03:07:30 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.180.13.142 with SMTP id h14mr1917661wic.3.1386068850565;
Tue, 03 Dec 2013 03:07:30 -0800 (PST)
Received: by 10.195.13.68 with HTTP; Tue, 3 Dec 2013 03:07:30 -0800 (PST)
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
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VnnpI-0004e7-UB
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Floating fees and SPV clients
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 03 Dec 2013 11:07:37 -0000
--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'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't care how many kilobytes their transactions are, and they wi=
ll 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 kiloby=
tes the paying transaction will be.</div>
<div class=3D"gmail_extra"><div><br></div>-- <br>--<br>Gavin Andresen<br>
</div></div>
--001a11c23dc279061d04ec9f4dc5--
|
