summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Whitlock <bip@mattwhitlock.name>2014-04-15 11:22:17 -0400
committerbitcoindev <bitcoindev@gnusha.org>2014-04-15 15:22:25 +0000
commite36d14f690c725d4fab8e27046ff844f601da3fd (patch)
treea176f1583d0e588b0aac624bbfe348f8f158a81b
parentfd1655b2b1f4907a16ce9624f0523f482ab3504f (diff)
downloadpi-bitcoindev-e36d14f690c725d4fab8e27046ff844f601da3fd.tar.gz
pi-bitcoindev-e36d14f690c725d4fab8e27046ff844f601da3fd.zip
Re: [Bitcoin-development] Bug in 2-of-3 transaction signing in Bitcoind?
-rw-r--r--2e/05d537cb9a63598d10d4dbf73f87ea8e2ccefd88
1 files changed, 88 insertions, 0 deletions
diff --git a/2e/05d537cb9a63598d10d4dbf73f87ea8e2ccefd b/2e/05d537cb9a63598d10d4dbf73f87ea8e2ccefd
new file mode 100644
index 000000000..891d1aa4a
--- /dev/null
+++ b/2e/05d537cb9a63598d10d4dbf73f87ea8e2ccefd
@@ -0,0 +1,88 @@
+Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
+ helo=mx.sourceforge.net)
+ by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <bip@mattwhitlock.name>) id 1Wa5Bp-0006GS-Pc
+ for bitcoin-development@lists.sourceforge.net;
+ Tue, 15 Apr 2014 15:22:25 +0000
+X-ACL-Warn:
+Received: from qmta05.westchester.pa.mail.comcast.net ([76.96.62.48])
+ by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
+ id 1Wa5Bn-0003Q3-Rz for bitcoin-development@lists.sourceforge.net;
+ Tue, 15 Apr 2014 15:22:25 +0000
+Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52])
+ by qmta05.westchester.pa.mail.comcast.net with comcast
+ id qB8a1n00417dt5G55FNJ9w; Tue, 15 Apr 2014 15:22:18 +0000
+Received: from crushinator.localnet ([IPv6:2601:6:4800:47f:219:d1ff:fe75:dc2f])
+ by omta13.westchester.pa.mail.comcast.net with comcast
+ id qFNH1n0154VnV2P3ZFNJdr; Tue, 15 Apr 2014 15:22:18 +0000
+From: Matt Whitlock <bip@mattwhitlock.name>
+To: Pieter Wuille <pieter.wuille@gmail.com>, Mike Hearn <mike@plan99.net>,
+ Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
+Date: Tue, 15 Apr 2014 11:22:17 -0400
+Message-ID: <2691411.GaPfSIFZEE@crushinator>
+User-Agent: KMail/4.12.4 (Linux/3.12.13-gentoo; KDE/4.12.4; x86_64; ; )
+In-Reply-To: <CAPg+sBgHZcdjRM+-UbSzuATBjj=yfBcqDMih+tAOYKBs=dLfWQ@mail.gmail.com>
+References: <1756895.gV83Q4MX2a@crushinator>
+ <CANEZrP1mgKRL9GTFtsokXv92LfDhOHR6uZ=KKn4RSopQpUc_Tw@mail.gmail.com>
+ <CAPg+sBgHZcdjRM+-UbSzuATBjj=yfBcqDMih+tAOYKBs=dLfWQ@mail.gmail.com>
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7Bit
+Content-Type: text/plain; charset="us-ascii"
+Sender: Matt Whitlock <bip@mattwhitlock.name>
+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.48 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: 1Wa5Bn-0003Q3-Rz
+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:22:26 -0000
+
+Thanks for the quick reply to both of you, Mike and Pieter.
+
+I feel foolish for posting to this list, because the debug.log does indeed say "inputs already spent." 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.
+
+Anyway, I'm sorry for the noise.
+
+
+On Tuesday, 15 April 2014, at 5:11 pm, Pieter Wuille wrote:
+> The first input seems to be already spent by another transaction
+> (which looks very similar).
+>
+> 0.9 should report a more detailed reason for rejection, by the way.
+>
+>
+>
+> On Tue, Apr 15, 2014 at 5:05 PM, Mike Hearn <mike@plan99.net> wrote:
+> > Check debug.log to find out the reason it was rejected.
+> >
+> >
+> >
+> > ------------------------------------------------------------------------------
+> > 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
+> >
+
+