Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UsVyw-0008WU-Ff for bitcoin-development@lists.sourceforge.net; Fri, 28 Jun 2013 10:32:46 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of googlemail.com designates 209.85.215.178 as permitted sender) client-ip=209.85.215.178; envelope-from=john.dillon892@googlemail.com; helo=mail-ea0-f178.google.com; Received: from mail-ea0-f178.google.com ([209.85.215.178]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UsVyu-0006mt-Jr for bitcoin-development@lists.sourceforge.net; Fri, 28 Jun 2013 10:32:46 +0000 Received: by mail-ea0-f178.google.com with SMTP id l15so940326eak.37 for ; Fri, 28 Jun 2013 03:32:38 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.14.220.66 with SMTP id n42mr13032663eep.67.1372415558301; Fri, 28 Jun 2013 03:32:38 -0700 (PDT) Received: by 10.223.12.131 with HTTP; Fri, 28 Jun 2013 03:32:38 -0700 (PDT) In-Reply-To: References: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com> Date: Fri, 28 Jun 2013 10:32:38 +0000 Message-ID: From: John Dillon To: Mike Hearn Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.4 (-) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (john.dillon892[at]googlemail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (john.dillon892[at]googlemail.com) -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: 1UsVyu-0006mt-Jr Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org 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: Fri, 28 Jun 2013 10:32:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Fri, Jun 28, 2013 at 10:20 AM, Mike Hearn wrote: > I suspect what you saw is mining nodes restarting and clearing their > mempools out rather than an explicit policy of replace by fee. Possibly, but it is a rather short window of opportunity and the mining node would have to be connected directly, to Peter's replace-by-fee node. I also took care to ensure transactions were only ever broadcast once. (I disabled the wallet rebroadcast mechanism) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJRzWYWAAoJEEWCsU4mNhiP3fIIAJLFxMnjI4BGRrNLsxs0hXp0 zDCgiZ6UnZa5JRcd/6KjV3hnPHwweGEjChGfrzY/Fxo4Pga1lQFlp8E8PaFUJq50 r6LTNJQLW50r5mFkZ6Mkh877WwX/OHBzkp8SqbbD7+dDBV7R9LqLYqLTHgObKxg1 V9UjGRJiMohW8HLdOzEXOz1ugoBCjR+vyQW5ZD2nZVcQlIhxSIgeC/M46oxMN7pE Y5EepCQehNPuc1On7TtJ9LlmFJ6Dvsl6dqwKNWMi1lgBTiw7abdTJne2B/KeDyom vhGuhmpMLGKKgJns3hne3yQM+Ivi3jLIHKejcoCm1JkSCdjw48XkyGd0V359M3w= =qyyq -----END PGP SIGNATURE-----