Re: Cold signing a transaction using bitcoin-qt

Quote from: oshirowanen on June 14, 2014, 07:08:26 PM

I want to send testnet bitcoin from mvNAGP5nNef6MHfB6Tcu426MJboBqrwJZV which has 0.57 TBTC http://tbtc.blockr.io/address/info/mvNAGP5nNef6MHfB6Tcu426MJboBqrwJZV. This is a public key for cold storage wallet.

So if I run listunspent, all I get is:

Code:

listunspent 1 9999999 '["mvNAGP5nNef6MHfB6Tcu426MJboBqrwJZV"']
[
]

Why is that?

I get the same result from both hot and cold wallets via bitcoin core.

I can't be certain without looking at the wallet, but I suspect that the reason is that the hot wallet doesn't have the mvNAGP5nNef6MHfB6Tcu426MJboBqrwJZV address, so it doesn't recognize the output as being spendable by that hot wallet. I also suspect that the cold wallet isn't synchronized and therefore doesn't know about the existence of the output.

Try this on each wallet:

Code:

validateaddress mvNAGP5nNef6MHfB6Tcu426MJboBqrwJZV

I suspect the hot wallet will return:
"ismine" : false,

And the cold wallet may (or may not) return:
"ismine" : true,

To get the scriptPubKey from the output you're trying to spend, you'd probably be better off running:

Code:

getrawtransaction 3d01e3b94195808a866bd75cd5a9a3d1d6ee0385fdd20025aacb4215bb9117e2

on the hot wallet. Then run decoderawtransaction on the output from that.

You should find the "hex" scriptPubKey in the output. Of course, getrawtransaction will only work on the hot wallet if you have txindex=1 in the bitcoin.conf file and have re-indexed the blockchain.