Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wa5V7-0001Xr-9H for bitcoin-development@lists.sourceforge.net; Tue, 15 Apr 2014 15:42:21 +0000 X-ACL-Warn: Received: from qmta02.westchester.pa.mail.comcast.net ([76.96.62.24]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Wa5V6-0001sa-EB for bitcoin-development@lists.sourceforge.net; Tue, 15 Apr 2014 15:42:21 +0000 Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta02.westchester.pa.mail.comcast.net with comcast id qCMN1n0051GhbT851FiFzL; Tue, 15 Apr 2014 15:42:15 +0000 Received: from crushinator.localnet ([IPv6:2601:6:4800:47f:219:d1ff:fe75:dc2f]) by omta07.westchester.pa.mail.comcast.net with comcast id qFiE1n00q4VnV2P3TFiEmY; Tue, 15 Apr 2014 15:42:15 +0000 From: Matt Whitlock To: Mike Hearn Date: Tue, 15 Apr 2014 11:42:14 -0400 Message-ID: <1832687.kEVurC5ttk@crushinator> User-Agent: KMail/4.12.4 (Linux/3.12.13-gentoo; KDE/4.12.4; x86_64; ; ) In-Reply-To: References: <1756895.gV83Q4MX2a@crushinator> <2691411.GaPfSIFZEE@crushinator> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: Matt Whitlock X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [76.96.62.24 listed in list.dnswl.org] 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: 1Wa5V6-0001sa-EB 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:42:21 -0000 On Tuesday, 15 April 2014, at 5:30 pm, Mike Hearn wrote: > > > > 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! Haha, yes, I know that. But we had been trying to get a 2-of-3 to be accepted by something for hours, and everything was rejecting it: Coinb.in, our local Bitcoind, the Eligius tx push form. Evidently something did accept it and we didn't notice. We're starting over again now and trying to reproduce the success (or failure).