From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XYHtC-0005VO-GA for bitcoin-development@lists.sourceforge.net; Sun, 28 Sep 2014 17:04:02 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([192.3.11.21]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XYHtB-0007BY-94 for bitcoin-development@lists.sourceforge.net; Sun, 28 Sep 2014 17:04:02 +0000 Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:be5f:f4ff:febf:4f76]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 8371610836AE for ; Sun, 28 Sep 2014 17:03:53 +0000 (UTC) From: Luke Dashjr To: bitcoin-development@lists.sourceforge.net Date: Sun, 28 Sep 2014 17:03:50 +0000 User-Agent: KMail/1.13.7 (Linux/3.15.5-gentoo; KDE/4.12.5; x86_64; ; ) References: <542778B0.7090202@thinlink.com> <20140928051553.GB11287@savin.petertodd.org> In-Reply-To: <20140928051553.GB11287@savin.petertodd.org> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201409281703.51377.luke@dashjr.org> X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1XYHtB-0007BY-94 Subject: Re: [Bitcoin-development] replace-by-fee v0.9.3 release 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: Sun, 28 Sep 2014 17:04:02 -0000 On Sunday, September 28, 2014 5:15:53 AM Peter Todd wrote: > On Sat, Sep 27, 2014 at 07:55:44PM -0700, Tom Harding wrote: > > On 9/25/2014 7:37 PM, Aaron Voisine wrote: > > > Of course you wouldn't want nodes to propagate alerts without > > > independently verifying them > > > > How would a node independently verify a double-spend alert, other than > > by having access to an actual signed double-spend? > > > > #4570 relays the first double-spend AS an alert. Running this branch on > > mainnet, I have been keeping a live list of relayed double-spend > > transactions at http://respends.thinlink.com > > Speaking of, I ported my replace-by-fee branch the recent v0.9.3 > release: https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.9.3 > > I actually ported it a few days ago; that release has been running on a > half-dozen or so nodes right now for a few days with no issues. > > The v0.9.3 release's scriptSig size limit increase adds a new category > of double-spending exploit. I'm not going to get time to add that > exploit to my replace-by-fee toolkit(1) for at least another week or so > though - pull-reqs accepted. > > 1) https://github.com/petertodd/replace-by-fee-tools Do you have or can you provide a version compatible with CPFP, such that a child paying a higher fee trumps the parent's replacement? Preferably something that will merge cleanly into 0.9.x-ljr :) Luke