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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1VnUmw-0005Zl-Ip
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Dec 2013 14:47:54 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.177 as permitted sender)
client-ip=209.85.212.177; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f177.google.com;
Received: from mail-wi0-f177.google.com ([209.85.212.177])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VnUmp-0003Za-Qh
for bitcoin-development@lists.sourceforge.net;
Mon, 02 Dec 2013 14:47:54 +0000
Received: by mail-wi0-f177.google.com with SMTP id cc10so4904020wib.10
for <bitcoin-development@lists.sourceforge.net>;
Mon, 02 Dec 2013 06:47:41 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=6EwICQm/EFRrtgkAzIqTkj44hzJTgbrSIiYujGsedqc=;
b=JafwhloRQUdRpnRgXawjHQoKZrK9QhomYc5bfO1Sjv0ob6iQcbtvSYCwtCydIqpATy
ZWhMP/71A78GOcb99lG5UYHBBOUSO2XM1T5Ka7Jsnr5V6eCHr+3ZToCdBsLJijgiNCOV
mlCTKTWuLReeFg2asx9r725bQSVNxJENTMoYy3JUpi54djMI854ATY6MOha5KAJvDKn7
Nnh3zZ1gL3M/wl+pY0iUmlXhyQmcyarJCsdOsBvjpwheKMUG6NgVyg71dscne0LBjrzG
ZoTPw+c3npB1O4RvQSQnmRkYtKiD9MQ8SYZFDGP6vqxDKe3H3dg5A1gLpIymIYYSiy1F
yoag==
X-Gm-Message-State: ALoCoQmcqgXpswh1VLNNfHL7gSRBqP1L7QrPWqJ+S0CPpPXJcRakv61sfSY/HHMIYsgJZysgtJnA
MIME-Version: 1.0
X-Received: by 10.180.19.201 with SMTP id h9mr18365376wie.36.1385995661557;
Mon, 02 Dec 2013 06:47:41 -0800 (PST)
Received: by 10.194.164.164 with HTTP; Mon, 2 Dec 2013 06:47:41 -0800 (PST)
In-Reply-To: <CANEZrP2hf2853w9f4__Ji9v3eRRU0u6pEzPxAmFN+iH067gtnA@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>
Date: Mon, 2 Dec 2013 09:47:41 -0500
Message-ID: <CAJHLa0M+HP4_irVyqG-J1+h6BRFHX2QZvDopxMxnD+j6ERzEzg@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
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 SPF_PASS SPF: sender matches SPF record
-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: 1VnUmp-0003Za-Qh
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:47:54 -0000
Current rough timeline proposed for 0.9 was end-of-January, IIRC.
On Mon, Dec 2, 2013 at 9:44 AM, Mike Hearn <mike@plan99.net> wrote:
> 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/
>
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
