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; 
MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Floating fees and SPV clients
Precedence: list

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/