From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 80302BC8 for ; Fri, 10 Jul 2015 16:26:23 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0D25015A for ; Fri, 10 Jul 2015 16:26:22 +0000 (UTC) Received: by igpy18 with SMTP id y18so16720589igp.0 for ; Fri, 10 Jul 2015 09:26:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/wFYt4/bDz2p62CH/y/p8ZqzST2Kw0dS4zf0fs1PWKQ=; b=MdIopSDsEhhaTSoIbroOwCztgsOWFC7HPug/ly5B2c/MotS2cr2YYFdmbasjXMq2i3 lZFnCEMhHH/NUuYkwQzaMC4l6SFz/PE75ZNkZm6V/TEch2n4wd9+qFYmew5wo2mBNCIQ 6LF7QD2Nd/SwD2DPqBVBbdDRu6N3Md6rz3wWksmd08PSg5mX9dy6PRHnt28HumIYlQPf rmkU5rop9nc8opwr4PpKzaBO7aFnnhsRrRRyZMW2WOltU9QiQdc+k6YRzY71hiOWrFvk xNyZkcYX6frF9nEVwWMyd3Dbsw8o+P8MUuMrz5pn/2HldPl4Pb4tiWfIiy9xI5AvyjkE jnug== MIME-Version: 1.0 X-Received: by 10.50.97.33 with SMTP id dx1mr3950136igb.1.1436545582547; Fri, 10 Jul 2015 09:26:22 -0700 (PDT) Received: by 10.107.17.212 with HTTP; Fri, 10 Jul 2015 09:26:22 -0700 (PDT) In-Reply-To: <837A1D9C-FD4E-4DF7-BE6B-4C90EB07C0A7@ricmoo.com> References: <6D3AACE5-D6CD-4785-8A55-F6DF0B94D927@ricmoo.com> <837A1D9C-FD4E-4DF7-BE6B-4C90EB07C0A7@ricmoo.com> Date: Fri, 10 Jul 2015 11:26:22 -0500 Message-ID: From: Dan Bryant To: Richard Moore Content-Type: text/plain; charset=UTF-8 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] Why not Child-Pays-For-Parent? X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: DKBryant@gmail.com List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jul 2015 16:26:23 -0000 Some miners have voluntarily deployed CPFP. I had a thread about it earlier this month where some other ideas got tossed around. https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009304.html The specific pull request to get it into the reference implementation is still open based on a merge conflict https://github.com/bitcoin/bitcoin/pull/1647 Peter Todd has another thread on RBF which you mentioned earlier http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2014-April/005620.html There is also a beautiful example of CPFP in action from Eligius in this transaction: https://blockchain.info/tx/4cc3e2b6407ae8cdc1fd62cb3235f9c92654277684da8970db19a0169e44c68c Follow the spent outputs and you will see the person is trying to incentive the transaction by upping the fees of dependent transactions. It set in the mempool until Eligius won a block, then it made it into the chain. CPFP still works, but only in an Eligius block (that I can see). So it's better than nothing.