On Tuesday, 15 April 2014, at 6:39 pm, Chris Beams wrote:
> Looks interesting. Is the source available?
The intent is to open-source it. We will do so when I'm confident that we have
all the kinks worked out.
Here's what it can do presently:
$ ./btctool
usage: ./btctool []
encode16
Encod
Hi Matt,
Looks interesting. Is the source available?
On Apr 15, 2014, at 6:27 PM, Matt Whitlock wrote:
On Tuesday, 15 April 2014, at 8:47 am, Mike Belshe wrote:
For what it is worth, I found btcd (the go implementation of bitcoind) has
much better error/diagnostics messages. It would have giv
On Tuesday, 15 April 2014, at 8:47 am, Mike Belshe wrote:
> 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 ver
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 wo
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
>
> 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!
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
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 wrote:
> Check debug.log to find out the reason it was rejected.
>
>
>
>
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 acclai
For the life of me, I cannot figure out what's wrong with this. It seems like
Bitcoind has lost its mind. I'm trying to redeem a 2-of-3 multisig P2SH output
using a raw transaction.
Here's the address that the P2SH output was sent to:
$ bitcoind createmultisig 2
'["03566474f987a012a69a0809725
10 matches
Mail list logo