From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wa5Js-0001A1-7x for bitcoin-development@lists.sourceforge.net; Tue, 15 Apr 2014 15:30:44 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.43 as permitted sender) client-ip=209.85.219.43; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f43.google.com; Received: from mail-oa0-f43.google.com ([209.85.219.43]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wa5Jq-0004bo-Ir for bitcoin-development@lists.sourceforge.net; Tue, 15 Apr 2014 15:30:44 +0000 Received: by mail-oa0-f43.google.com with SMTP id eb12so10943224oac.2 for ; Tue, 15 Apr 2014 08:30:37 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.219.167 with SMTP id pp7mr735918obc.85.1397575837261; Tue, 15 Apr 2014 08:30:37 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.96.180 with HTTP; Tue, 15 Apr 2014 08:30:37 -0700 (PDT) In-Reply-To: <2691411.GaPfSIFZEE@crushinator> References: <1756895.gV83Q4MX2a@crushinator> <2691411.GaPfSIFZEE@crushinator> Date: Tue, 15 Apr 2014 17:30:37 +0200 X-Google-Sender-Auth: TnNBlAXSb6jY2naWZjW0wjNghQk Message-ID: From: Mike Hearn To: Matt Whitlock Content-Type: multipart/alternative; boundary=089e0141ab8253aa0f04f7167b3a X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1Wa5Jq-0004bo-Ir Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Bug in 2-of-3 transaction signing in Bitcoind? 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: Tue, 15 Apr 2014 15:30:44 -0000 --089e0141ab8253aa0f04f7167b3a Content-Type: text/plain; charset=UTF-8 > > That's so weird, though, because we haven't been able to get anything to > accept the transaction, seemingly, and yet it was accepted into the block > chain 15 blocks ago. If the tx is already in the block chain then it won't be accepted again, because it would be double spending itself! --089e0141ab8253aa0f04f7167b3a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That's so weird, though, because we haven= 9;t been able to get anything to accept the transaction, seemingly, and yet= it was accepted into the block chain 15 blocks ago.

If the tx is already in the block chain then it won'= ;t be accepted again, because it would be double spending itself!=C2=A0
--089e0141ab8253aa0f04f7167b3a--