Indeed you have!

Private key for 17QgF3oJCLAvzGg2hxPX6rMhS5tKebWsiz is 5JmDdyq8QKDf2mtTWxpWcsfVrWPQSj4fkH8HeUBahCtHuP9ov6x.

2 BTC sent to your tip jar (txid 7c8d9f94b616282413519e05627579d8acee37c3bb7372d27de1886fc0624ecd).

Your help has been much appreciated.

Yup - I will add that as a comment in usage.html.


Yup - that's it - you must be getting close now.

The txid must be the one for the tx that you issued to *send* the 0.0015 to the address that you generated offline (so it's different for everyone).

You can find the txid either through your Bitcoin client or on blockchain.info (search for the address you generated) and the tx should be there.

BTW - I will not be accepting attempts from members that were registered *after* the OP was posted.

(as it would be rather too easy money if I were to let someone who's already done this to just repeat the work to get the rest of the pot with new accounts)

Yup - still 8 BTC remaining (in the title of the OP) and only one other member working on it at the moment.

Thank you - and have sent 2 BTC (txid: 966e4ecc3c40828e63cd012c98f947494fd6aa907e0a993bf9926538aed6cd94) - good to know that the system is working (and yes you could always use USB rather than webcams - just depends upon your level of paranoia).

Proof that jl2012's answer was correct is that the private key for the 1ELPYyJKLfeQHPu3FCSSKfFHjhCkEbapct that was generated "offline" is 5Jo14o6CAYQin8WgqR59s1CQ4Hh4VirsnBSEizfE7sFb5r75i8g (so don't ever send BTC to that address again).


Okay - if you want to keep the private and two public keys you originally created then check the instructions about "restoring" at the end of "usage.html" otherwise you can just start from scratch ... or ... you could always "scan" the signtx script and send it across via QR.

Thanks for the info John - will also add that to the doco!

Am tired now and need to sleep - will continue this in another 8 hours or so.

Can see John's tx now (he's half-way there).

I think that 16 GB is required (although maybe this could be changed).

I have sent coins many times when being more than 100 blocks "behind" so I don't think it could be that.

For the "online" computer - absolutely (that's what I am using) - for the "offline" one you need to use the LiveOS (which is Linux).

Hmm... I can't see it either - perhaps not enough funds had arrived on your client yet (perhaps a "safety" measure imposed to stop you attempting to spend funds not yet seen)?

You can send it now (no need to wait but entirely up to you of course - your client doesn't need to be "up to date" to do that provided that it can see it has enough funds).

Okay - I should have documented that you need to wait until it says "Finished building 'bitcoind'..." (notes taken) - if the build was not completed then you will need to run the script "./build-bitcoin" (haven't seen the tx though yet - sure you sent it?).

Yes it is (thus only the need to use the Password once you've got it set up).

Am interested in the "crash" - any reason you think (perhaps it hadn't finished building)?

The usage.html explains exactly how (you will need to enter the Password again but not the User Key as the GPG password has been "scypt" encrypted).

I have done this at least 5 or 6 times in the last few days so don't worry it *really should* work (and in the event you really can't recover 0.01 BTC then I will gladly refund it).

(in my own testing I have lost only around 0.005 Bitcoin due to a stupid mistake)

John - please note that the "vout" is almost certainly #1 (not #0) if you are using the "reference client" (due to a bug with the way that change addresses are *not* randomly allocated in the [usual] case of their being 2 "unspent outputs").

Hmm... am not sure why this would occur then (am not a "hardware" guy really at all) and am not sure how you could proceed from here but if the 10 BTC isn't dispersed within the next week then I will send you 1 BTC for your attempt anyway (sorry I can't be of more help but hope you understand that others could just follow up with the same thing).

Your "offline" computer is 32 bit?

Yup - send say 0.0095 to the address and let the client add the 0.0005 tx fee (then the offline tx should be written to send back 0.009 to pay another 0.0005 tx fee).