I ran into a similar problem trying to follow the
tutorial here for offline transactions:
james@torchlight:~/coinjoin$ sx mktx jun272014pool.tx --input 43f1c3e735560f7b1e4c396a55a2e62d2e83b7c4ed1efc5a7d29358c84ca7807:1 --output 1Ft1DZ4EcpH1jFttDoPwsFbe11a6diyZ1H:25000000
Added input 43f1c3e735560f7b1e4c396a55a2e62d2e83b7c4ed1efc5a7d29358c84ca7807:1
Added output sending 25000000 Satoshis to 1Ft1DZ4EcpH1jFttDoPwsFbe11a6diyZ1H.
james@torchlight:~/coinjoin$ DECODED_ADDR=$(cat 1ExAmpLEf.key | sx addr | sx decode-addr)
james@torchlight:~/coinjoin$ PREVOUT_SCRIPT=$(sx rawscript dup hash160 [ $DECODED_ADDR ] equalverify checksig)
james@torchlight:~/coinjoin$ SIGNATURE=$(cat 1ExAmpLEf.key | sx sign-input jun272014pool.tx 0 $PREVOUT_SCRIPT)
james@torchlight:~/coinjoin$ sx rawscript [ $SIGNATURE ] [ $(cat 1ExAmpLEf.key | sx pubkey) ] | sx set-input jun272014pool.tx 0 > signed.tx
Usage: set-input FILENAME N SIGNATURE_AND_PUBKEY_SCRIPT
After some trial and error, I find this works:
james@torchlight:~/coinjoin$ sx set-input jun272014pool.tx 0 $(sx rawscript [ $SIGNATURE ] [ $(cat 1ExAmpLEf.key | sx pubkey) ]) > signed.tx
james@torchlight:~/coinjoin$ sx validtx signed.tx
Status: Success
I also found that Bitcoind 0.9.2
seems to ignore transactions sent with sendtx-node. This appears to be a regression, since I believe I had it work at least once in the past. I since updated and rebuilt sx tools. I may have upgraded the bitcoind node to 0.9.2 (from 0.8.x) as well.
I really need to keep better maintenance logs
PS: I briefly considered posting on the unsystem forum, but I see no categories. I have always thought web-forums are a poor imitation of USENET, but doing away with categories altogether (because people don't use them?) is worse IMO.