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
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1VnUk6-0004jI-7L
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Dec 2013 14:44:58 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.175 as permitted sender)
client-ip=209.85.214.175; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f175.google.com;
Received: from mail-ob0-f175.google.com ([209.85.214.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VnUk4-0000PS-DA
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Dec 2013 14:44:58 +0000
Received: by mail-ob0-f175.google.com with SMTP id uz6so12771543obc.20
for <bitcoin-development@lists.sourceforge.net>;
Mon, 02 Dec 2013 06:44:51 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.196.3 with SMTP id ii3mr55972175obc.11.1385995491010;
Mon, 02 Dec 2013 06:44:51 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.3.134 with HTTP; Mon, 2 Dec 2013 06:44:50 -0800 (PST)
In-Reply-To: <CAJHLa0P_uzEQ2OG2FTXyD2Zw4RzujNBxKbKD04CSS1sLNpLUUQ@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>
Date: Mon, 2 Dec 2013 15:44:50 +0100
X-Google-Sender-Auth: MMNRT2PfRhWOF3cqPg99lQxThJc
Message-ID: <CANEZrP2hf2853w9f4__Ji9v3eRRU0u6pEzPxAmFN+iH067gtnA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=089e015383e4e6eeea04ec8e384b
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: plan99.net]
-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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1VnUk4-0000PS-DA
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: Mon, 02 Dec 2013 14:44:58 -0000
--089e015383e4e6eeea04ec8e384b
Content-Type: text/plain; charset=UTF-8
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.
There's code pending review to implement PPv1 in bitcoinj, unfortunately
it's currently not passing unit tests and the author can't figure out why.
I didn't have time to debug it yet myself. I'm hopeful we can get it
working and merged by EOY.
It may be time to start talking about timelines for 0.9. I am wondering if
floating fees should be broken out of the 0.9 release and launched in a
quick 0.10 followup - if that were to be done then I think 0.9 could go to
beta relatively soon, like early next year. There have been a lot of
improvements already and it'd be a shame to block them all further.
On Mon, Dec 2, 2013 at 3:37 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> On Mon, Dec 2, 2013 at 9:33 AM, Mike Hearn <mike@plan99.net> wrote:
> > "The payment protocol at least would need some notion of fee, or possibly
> > (better?) the ability for a recipient to specify some inputs as well as
> some
> > outputs."
>
> <vendor hat: on>
>
> BitPay noticed this detail last week. We were noticing that some
> transactions were not even reaching our bitcoind border routers (edge
> nodes), due to low/no fees. That led to a long discussion of all
> things fee-related. SPV fees are a big issue. Getting
> child-pays-for-parent in some form out to miners is another. Getting
> a smart, dynamic fee market Gavin mentions is a big need.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
--089e015383e4e6eeea04ec8e384b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">PPv1 doesn't have any notion of fee unfortunately. I s=
uppose it could be added easily, but we also need to launch the existing fe=
ature set.<div><br></div><div>There's code pending review to implement =
PPv1 in bitcoinj, unfortunately it's currently not passing unit tests a=
nd the author can't figure out why. I didn't have time to debug it =
yet myself. I'm hopeful we can get it working and merged by EOY.</div>
<div><br></div><div>It may be time to start talking about timelines for 0.9=
. I am wondering if floating fees should be broken out of the 0.9 release a=
nd launched in a quick 0.10 followup - if that were to be done then I think=
0.9 could go to beta relatively soon, like early next year. There have bee=
n a lot of improvements already and it'd be a shame to block them all f=
urther.</div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Dec 2, 2013 at 3:37 PM, Jeff Garzik <span dir=3D"ltr"><<=
a href=3D"mailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</=
a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Mon, Dec 2, 2013 at 9:3=
3 AM, Mike Hearn <<a href=3D"mailto:mike@plan99.net">mike@plan99.net</a>=
> wrote:<br>
> "The payment protocol at least would need some notion of fee, or =
possibly<br>
> (better?) the ability for a recipient to specify some inputs as well a=
s some<br>
> outputs."<br>
<br>
</div><vendor hat: on><br>
<br>
BitPay noticed this detail last week. =C2=A0We were noticing that some<br>
transactions were not even reaching our bitcoind border routers (edge<br>
nodes), due to low/no fees. =C2=A0That led to a long discussion of all<br>
things fee-related. =C2=A0SPV fees are a big issue. =C2=A0Getting<br>
child-pays-for-parent in some form out to miners is another. =C2=A0Getting<=
br>
a smart, dynamic fee market Gavin mentions is a big need.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
</font></span></blockquote></div><br></div>
--089e015383e4e6eeea04ec8e384b--
|
