[ANN] CIYAM Safe - offline tx's using QR codes for comms

[John (John K.)]

Hmm I'm wondering on how to decrypt the PGP message (the address's privkeys) generated when the address is generated. It requires a different key from what I've generated earlier.

[CIYAM]

Hmm I'm wondering on how to decrypt the PGP message (the address's privkeys) generated when the address is generated. It requires a different key from what I've generated earlier.

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 (John K.)]

PS: Is the install 'persistent'? I'm restarting the offline computer due to a crash when loading ./bitcoin.

[CIYAM]

PS: Is the install 'persistent'? I'm restarting the offline computer due to a crash when loading ./bitcoin.

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)?

[John (John K.)]

PS: Is the install 'persistent'? I'm restarting the offline computer due to a crash when loading ./bitcoin.

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?

Yep, confirmed that the persistence is working fine. I would attribute it to the ./bitcoin script and the sluggish performance of my old netbook. The cursor and keyboard locked up, and I had to pull the plug for a cold reboot.

I'm sending the initial coins to the address generated at 17QgF3oJCLAvzGg2hxPX6rMhS5tKebWsiz now.

PS: have to catch up my blockchain ... 

[CIYAM]

Yep, confirmed that the persistence is working fine. I would attribute it to the ./bitcoin script and the sluggish performance of my old netbook. The cursor and keyboard locked up, and I had to pull the plug for a cold reboot.

I'm sending the initial coins to the address generated at 17QgF3oJCLAvzGg2hxPX6rMhS5tKebWsiz now.

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?).

[John (John K.)]

Yep, confirmed that the persistence is working fine. I would attribute it to the ./bitcoin script and the sluggish performance of my old netbook. The cursor and keyboard locked up, and I had to pull the plug for a cold reboot.

I'm sending the initial coins to the address generated at 17QgF3oJCLAvzGg2hxPX6rMhS5tKebWsiz now.

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?).

I'm working through the last 100+- blocks or so before sending the tx - had to download the blockchain for my other cold wallet.

[CIYAM]

I'm working through the last 100+- blocks or so before sending the tx - had to download the blockchain for my other cold wallet.

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).

[John (John K.)]

I'm working through the last 100+- blocks or so before sending the tx - had to download the blockchain for my other cold wallet.

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).

Oh, okay - just sent the tx in at 33437f32b09cea85639718ef5041a3d537b52032cdd39f1a3985e601b3e8182e . It wasn't successfully broadcasted yet strangely.

[CIYAM]

Oh, okay - just sent the tx in at 33437f32b09cea85639718ef5041a3d537b52032cdd39f1a3985e601b3e8182e . It wasn't successfully broadcasted yet strangely.

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)?

[BCB]

Can I run this on a windows xp machine?

[CIYAM]

Can I run this on a windows xp machine?

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

[John (John K.)]

Oh, okay - just sent the tx in at 33437f32b09cea85639718ef5041a3d537b52032cdd39f1a3985e601b3e8182e . It wasn't successfully broadcasted yet strangely.

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)?

There's more than enough preconfirmed coins in the system. I would wager a guess that bitcoin-qt needs to catch up with all blocks before sending out a tx to thwart potential double spends.

[BCB]

Can I run this on a windows xp machine?

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

Thx.

What size is required for the USB drive?

[CIYAM]

There's more than enough preconfirmed coins in the system. I would wager a guess that bitcoin-qt needs to catch up with all blocks before sending out a tx to thwart potential double spends.

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

[CIYAM]

What size is required for the USB drive?

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

[BCB]

Oh, okay - just sent the tx in at 33437f32b09cea85639718ef5041a3d537b52032cdd39f1a3985e601b3e8182e . It wasn't successfully broadcasted yet strangely.

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)?

There's more than enough preconfirmed coins in the system. I would wager a guess that bitcoin-qt needs to catch up with all blocks before sending out a tx to thwart potential double spends.

You coins just hit the blockchain!

[CIYAM]

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

[John (John K.)]

There's more than enough preconfirmed coins in the system. I would wager a guess that bitcoin-qt needs to catch up with all blocks before sending out a tx to thwart potential double spends.

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

Yep - It has finally went through moments ago: http://blockchain.info/address/17QgF3oJCLAvzGg2hxPX6rMhS5tKebWsiz
Whew.

What size is required for the USB drive?

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

I'm running the system on a 4GB drive so I think 4 and above is okay. The raw is approx 2.7GB.

[CIYAM]

I'm running the system on a 4GB drive so I think 4 and above is okay. The raw is approx 2.7GB.

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.