Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <gavinandresen@gmail.com>) id 1S2RVk-0004pv-Pt for bitcoin-development@lists.sourceforge.net; Tue, 28 Feb 2012 18:10:52 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=gavinandresen@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1S2RVf-0000tN-97 for bitcoin-development@lists.sourceforge.net; Tue, 28 Feb 2012 18:10:52 +0000 Received: by wgbdr1 with SMTP id dr1so3200765wgb.10 for <bitcoin-development@lists.sourceforge.net>; Tue, 28 Feb 2012 10:10:41 -0800 (PST) Received-SPF: pass (google.com: domain of gavinandresen@gmail.com designates 10.180.24.68 as permitted sender) client-ip=10.180.24.68; Authentication-Results: mr.google.com; spf=pass (google.com: domain of gavinandresen@gmail.com designates 10.180.24.68 as permitted sender) smtp.mail=gavinandresen@gmail.com; dkim=pass header.i=gavinandresen@gmail.com Received: from mr.google.com ([10.180.24.68]) by 10.180.24.68 with SMTP id s4mr4681610wif.22.1330452641275 (num_hops = 1); Tue, 28 Feb 2012 10:10:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.24.68 with SMTP id s4mr3768815wif.22.1330452641229; Tue, 28 Feb 2012 10:10:41 -0800 (PST) Received: by 10.223.121.197 with HTTP; Tue, 28 Feb 2012 10:10:41 -0800 (PST) In-Reply-To: <CAPg+sBhb+gYMwp1OJuCHYt5=BU63=YBWOFaLLthHBkN_U-scaA@mail.gmail.com> References: <CAPg+sBhb+gYMwp1OJuCHYt5=BU63=YBWOFaLLthHBkN_U-scaA@mail.gmail.com> Date: Tue, 28 Feb 2012 13:10:41 -0500 Message-ID: <CABsx9T3-H9uSNjQ2mXTZ9rA62Gn7vWe8Z+GK2rQTzrvcN_PRQg@mail.gmail.com> From: Gavin Andresen <gavinandresen@gmail.com> To: Pieter Wuille <pieter.wuille@gmail.com> Content-Type: multipart/alternative; boundary=f46d043894c1122a6c04ba0a259b X-Spam-Score: -0.8 (/) 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 (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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 -0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1S2RVf-0000tN-97 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Duplicate transactions vulnerability X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Tue, 28 Feb 2012 18:10:52 -0000 --f46d043894c1122a6c04ba0a259b Content-Type: text/plain; charset=ISO-8859-1 > > The purpose of this mail is asking for support for adding this rule to > the protocol rules. If there is consensus this rule is the solution, I > hope pools and miners can agree to update their nodes without lengthy > coinbase-flagging procedure that would only delay a solution. So, who > is in favor? Pieter > Most of you might already know this, but I'm strongly in favor of doing this as soon as possible. -- -- Gavin Andresen --f46d043894c1122a6c04ba0a259b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi= n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The purpose of th= is mail is asking for support for adding this rule to<br> the protocol rules. If there is consensus this rule is the solution, I<br> hope pools and miners can agree to update their nodes without lengthy<br> coinbase-flagging procedure that would only delay a solution. So, who<br> is in favor?=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"marg= in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Pieter<br></bloc= kquote><div><br></div><div style>Most of you might already know this, but I= 'm strongly in favor of doing this as soon as possible.<span style=3D"b= ackground-color:transparent">=A0</span></div> </div><div><br></div>-- <br>--<br>Gavin Andresen<br><br> --f46d043894c1122a6c04ba0a259b--