Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YM0DK-0000f2-Ce for bitcoin-development@lists.sourceforge.net; Thu, 12 Feb 2015 20:18:18 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.149.82 as permitted sender) client-ip=62.13.149.82; envelope-from=pete@petertodd.org; helo=outmail149082.authsmtp.co.uk; Received: from outmail149082.authsmtp.co.uk ([62.13.149.82]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1YM0DI-0000Ak-RB for bitcoin-development@lists.sourceforge.net; Thu, 12 Feb 2015 20:18:18 +0000 Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt16.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t1CKIALG021334; Thu, 12 Feb 2015 20:18:10 GMT Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com [75.119.251.161]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t1CKI6Ft024448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Feb 2015 20:18:08 GMT Date: Thu, 12 Feb 2015 15:18:05 -0500 From: Peter Todd To: Gregory Maxwell Message-ID: <20150212201805.GA27692@savin.petertodd.org> References: <20150212064719.GA6563@savin.petertodd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: 42e84e12-b2f4-11e4-9f74-002590a135d3 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdwAUHlAWAgsB AmMbWVReUVV7WWo7 bA9PbARUfEhLXhtr VklWR1pVCwQmRR1y fWcYJF1ydQFCfHY+ ZERiWHQVWEYvfUIo Q0xJR29QYXphaTUb TUkOcAdJcANIexZF O1F8UScOLwdSbGoL NQ4vNDcwO3BTJTpY RgYVKF8UXXNDBDMk QxkJEHAlDAgLSih7 MURgcwZaRFwabi0A X-Authentic-SMTP: 61633532353630.1024:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 75.119.251.161/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1YM0DI-0000Ak-RB Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 20:18:18 -0000 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 12, 2015 at 07:49:29PM +0000, Gregory Maxwell wrote: > One challenge is that without rather smart child-pays-for-parent logic > the positive argument for replace by fee doesn't really work. That's actually incorrect now, as a mechanism for implementing scorched-earth without child-pays-for-parent using SIGHASH_ANYONECANPAY is available: http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg= 05211.html I greatly prefer this mechanism as it's an opt-in mechanism - many wallets double-spend on occasion by accident - and can have the incentives be adjusted to suit the % of hashing power that actual supports replace-by-fee. (and the % probability you'll see the doublespend) My patch implements 90% of the logic required for the above to work, however I've intentionally limited the total depth of recursion when the replacement is being evaluated as an interm anti-DoS measure in the spirit of belt-and-suspenders engineering. This can certainly be improved on, e.g. by limiting total mempool size. --=20 'peter'[:-1]@petertodd.org 00000000000000000a16bcc766361414571a5f961698acc46c27bd79c26ac15c --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQGrBAEBCACVBQJU3Qp5XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw MDAwMDAwMDAwMDAwMDAwODkwNTQ3MGZiYTc5MmM4OTkxY2JjMmJiN2Q0MmI5NTQz Njk0ODhhZGRhM2IyMGUvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftaQAf/Qr2ybwer4XOdapIVd/ryhPA4 RDSVuOFvdq1Pp+oLzvTz9UL/yc/i8ND0pq/WASATuUcLyIuzYYGuxhd3Fu36cg85 084+u1En41hrSOxOfeOmVLWAiTMWw8pJJ3yoP84AGhmERQbT61Z6Yr591+RZuTQE 9J6vYlFu9X3Apkt5b6R1atFeAaRkEf7eMhv+bFd96zsK1Pz2PX32b6vbTlnDjTgJ nOeJkts7IYzG2PqeAaqfxjMFFn+piFiZPdK54eh73ghiFd48ksadqf2KciEXT9Iu CCqQw2/GQBkYYcNVUS77bPviwoh3piRhktl5giQAEZOQdvSTOgDRDZ8tr5QjYQ== =Thyj -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7--