From: Pieter Wuille <pieter.wuille@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bug in 2-of-3 transaction signing in Bitcoind?
Date: Tue, 15 Apr 2014 17:11:40 +0200 [thread overview]
Message-ID: <CAPg+sBgHZcdjRM+-UbSzuATBjj=yfBcqDMih+tAOYKBs=dLfWQ@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP1mgKRL9GTFtsokXv92LfDhOHR6uZ=KKn4RSopQpUc_Tw@mail.gmail.com>
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
>
next prev parent reply other threads:[~2014-04-15 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 15:00 [Bitcoin-development] Bug in 2-of-3 transaction signing in Bitcoind? Matt Whitlock
2014-04-15 15:05 ` Mike Hearn
2014-04-15 15:11 ` Pieter Wuille [this message]
2014-04-15 15:22 ` Matt Whitlock
2014-04-15 15:30 ` Mike Hearn
2014-04-15 15:42 ` Matt Whitlock
2014-04-15 15:47 ` Mike Belshe
2014-04-15 16:27 ` Matt Whitlock
2014-04-15 16:39 ` Chris Beams
2014-04-15 16:45 ` Matt Whitlock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPg+sBgHZcdjRM+-UbSzuATBjj=yfBcqDMih+tAOYKBs=dLfWQ@mail.gmail.com' \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox