From: Matt Whitlock <bip@mattwhitlock.name>
To: Mike Hearn <mike@plan99.net>
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: <CANEZrP1XS3iR2Ju9rbX81eU1nUSrQJUzjrVaE2HQnrJnQYRMKQ@mail.gmail.com>
References: <1756895.gV83Q4MX2a@crushinator> <2691411.GaPfSIFZEE@crushinator>
	<CANEZrP1XS3iR2Ju9rbX81eU1nUSrQJUzjrVaE2HQnrJnQYRMKQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: Matt Whitlock <bip@mattwhitlock.name>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bug in 2-of-3 transaction signing in
	Bitcoind?
Precedence: list

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).