Skip to main content
5 events
when toggle format what by license comment
Apr 6, 2014 at 21:34 comment added Phil Dann Ward @KJO Your suggestion led me to bitcoin.stackexchange.com/questions/5424/… and bitcointalk.org/index.php?topic=104512.0 Using either method avoids the JSON parsing error ( :-) ) but trying it out on a worked example people.xiph.org/~greg/signdemo.txt gives me complete=false where I'd expect to recreate the example to get complete=true ( :-( ). I shall keep banging my head against the wall trying to work out why I seem to be unable to properly process raw transactions but thanks for getting me a few steps closer.
Apr 6, 2014 at 21:24 vote accept Phil Dann Ward
Apr 5, 2014 at 18:35 comment added KJ O @PhilDannWard Try enclosing everything in triple-quotes. And if you're on Windows--it seems like when I was messing around with Namecoin--I believe CMD needs \newlines to play nice with JSON (Though I'm probably very wrong.)
Apr 5, 2014 at 15:50 comment added Phil Dann Ward Got the server running on Windows 7 (thanks) and I can successfully issue commands using bitcoind (e.g. getinfo, decoderawtransaction, etc) but all my attempts to put any sort of JSON data into a command fails...for example...bitcoind signrawtransaction <transactioninhex> [{"txid":"bc2964822afc7ed5cf0f6f412cc61a086ff765584d6cb910a2bbe8d4f045eedf","vout":0,"scriptPubKey":"76a91406f1b6703d3f56427bfcfd372f952d50d04b64bd88ac"}] error: Error parsing JSON:[{txid:bc2964822afc7ed5cf0f6f412cc61a086ff765584d6cb910a2bbe8d4f045eedf,vout:0,scriptPubKey:76a91406f1b6703d3f56427bfcfd372f952d50d04b64bd88ac}]
Apr 5, 2014 at 3:55 history answered Richard Kiss CC BY-SA 3.0