Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wa5aW-0001qy-91 for bitcoin-development@lists.sourceforge.net; Tue, 15 Apr 2014 15:47:56 +0000 X-ACL-Warn: Received: from mail-qc0-f171.google.com ([209.85.216.171]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wa5aV-0004GX-4P for bitcoin-development@lists.sourceforge.net; Tue, 15 Apr 2014 15:47:56 +0000 Received: by mail-qc0-f171.google.com with SMTP id c9so10706121qcz.30 for ; Tue, 15 Apr 2014 08:47:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+iHOVK3rcJdSMn2Dj7o1y8bD4fyKZYWR44OCMqOZTPs=; b=WRRpGbRChD0asykncsYRUPYtNVrw+CLoXCSwXfbY7wengQmRkHEjwh38cZHD4Llg41 zzuzwVqLsEbKgPyA5Eb3llYSw3a/9HhlMRGoHAyCg8Mva24tiLMhz0FQMY3OCBSZXzlm UAHKBFygETX9Hk66bx6jxbR0mDh8XAry2No2IozvYS0Vkypa6dGQpLUw+2OvYeyjN++p QebTYM5m/RdinvVgzbF7uBMIDT3YxiG+A2bnU+S5SUgc9bcixcv/rbPWh2A58w5yFTfY We5FzmyutYMzwG1eiMRVKWZAnIIUq4unsCRzgjgpZiMQ7GAWKrz/kmrCtt3hRcGbU78V 0x2Q== X-Gm-Message-State: ALoCoQkBYAmjlk7zvmgVLP96AJgC0gPLEZtC62XmIPFxwwqW3o1zKoBbsCLY7t41zgRYm74dlUtB MIME-Version: 1.0 X-Received: by 10.224.114.209 with SMTP id f17mr3804243qaq.40.1397576853096; Tue, 15 Apr 2014 08:47:33 -0700 (PDT) Received: by 10.96.82.104 with HTTP; Tue, 15 Apr 2014 08:47:33 -0700 (PDT) In-Reply-To: <1832687.kEVurC5ttk@crushinator> References: <1756895.gV83Q4MX2a@crushinator> <2691411.GaPfSIFZEE@crushinator> <1832687.kEVurC5ttk@crushinator> Date: Tue, 15 Apr 2014 08:47:33 -0700 Message-ID: From: Mike Belshe To: Matt Whitlock Content-Type: multipart/alternative; boundary=047d7bdc19ace029bc04f716b729 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1Wa5aV-0004GX-4P 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:47:56 -0000 --047d7bdc19ace029bc04f716b729 Content-Type: text/plain; charset=UTF-8 For what it is worth, I found btcd (the go implementation of bitcoind) has much better error/diagnostics messages. It would have given you more than "-22 TX Rejected". I used it to debug my own multi-sig transactions and it was very helpful. Mike On Tue, Apr 15, 2014 at 8:42 AM, Matt Whitlock wrote: > 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). > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/NeoTech > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --047d7bdc19ace029bc04f716b729 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
For what it is worth, I found btcd (the go implementation = of bitcoind) has much better error/diagnostics messages. =C2=A0It would hav= e given you more than "-22 TX Rejected". =C2=A0I used it to debug= my own multi-sig transactions and it was very helpful.

Mike



On Tue, Apr 15, 2014 at 8:42 AM= , Matt Whitlock <bip@mattwhitlock.name> wrote:
On T= uesday, 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 t= he 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: Coi= nb.in, our local Bitcoind, the Eligius tx push form. Evidently something di= d accept it and we didn't notice. We're starting over again now and= trying to reproduce the success (or failure).

---------------------------------------------------------------------------= ---
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases = and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/s= fu/NeoTech
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--047d7bdc19ace029bc04f716b729--