1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
|
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 <mike@belshe.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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>
<CANEZrP1XS3iR2Ju9rbX81eU1nUSrQJUzjrVaE2HQnrJnQYRMKQ@mail.gmail.com>
<1832687.kEVurC5ttk@crushinator>
Date: Tue, 15 Apr 2014 08:47:33 -0700
Message-ID: <CABaLYCu7by9AsurAcjzjo4QR_3Ln6DZrq7GPH_KxTokUbGTEeg@mail.gmail.com>
From: Mike Belshe <mike@belshe.com>
To: Matt Whitlock <bip@mattwhitlock.name>
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 <bitcoin-development@lists.sourceforge.net>
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: <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, 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 <bip@mattwhitlock.name>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
<div dir=3D"ltr">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.<div>
<br></div><div><div>Mike</div><div><br></div></div></div><div class=3D"gmai=
l_extra"><br><br><div class=3D"gmail_quote">On Tue, Apr 15, 2014 at 8:42 AM=
, Matt Whitlock <span dir=3D"ltr"><<a href=3D"mailto:bip@mattwhitlock.na=
me" target=3D"_blank">bip@mattwhitlock.name</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On T=
uesday, 15 April 2014, at 5:30 pm, Mike Hearn wrote:<br>
> ><br>
> > That's so weird, though, because we haven't been able to =
get anything to<br>
> > accept the transaction, seemingly, and yet it was accepted into t=
he block<br>
> > chain 15 blocks ago.<br>
><br>
><br>
> If the tx is already in the block chain then it won't be accepted =
again,<br>
> because it would be double spending itself!<br>
<br>
</div></div>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).<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/NeoTech" target=3D"_blank">http://p.sf.net/s=
fu/NeoTech</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--047d7bdc19ace029bc04f716b729--
|
