Topic: [ANN] CIYAM Safe - offline tx's using QR codes for comms - page 4. (Read 6159 times)
Can I run this on a windows xp machine?
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)?
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).
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).
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.
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.
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.
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?).
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?
I'm sending the initial coins to the address generated at 17QgF3oJCLAvzGg2hxPX6rMhS5tKebWsiz now.
PS: have to catch up my blockchain ...
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)?
PS: Is the install 'persistent'? I'm restarting the offline computer due to a crash when loading ./bitcoin.
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)
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.
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").
The windpad is 64bit but it has no problem in loading 32bit systems like android-x86 and windows
EEEPC is certainly 32bit only system
EEEPC is certainly 32bit only system
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).
Yes, I use the ImageWriter for windows.
Your "offline" computer is 32 bit?
The windpad is 64bit but it has no problem in loading 32bit systems like android-x86 and windows
EEEPC is certainly 32bit only system
Yes, I use the ImageWriter for windows.
Your "offline" computer is 32 bit?
Do I first send some change to the address generated via a regular transaction? Then use the offline computer to send the change back again?
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).
The system fail to boot on both MSI WindPad 110w and ASUS EEEPC 900
On WindPad, no matter I choose "failsafe" or not, it crashed with a messed screen
On EEEPC, no matter I choose "failsafe" or not, after the penguin screen, it stopped at "[sdd] No Caching mode pange present" and "[sdd] Assuming drive cache: write through". About 2 minute later, the system reboot autometically
On WindPad, no matter I choose "failsafe" or not, it crashed with a messed screen
On EEEPC, no matter I choose "failsafe" or not, after the penguin screen, it stopped at "[sdd] No Caching mode pange present" and "[sdd] Assuming drive cache: write through". About 2 minute later, the system reboot autometically
Okay - you did use ImageWriter to create the USB image from the .raw file (also note that this is a 32 bit image)?
Yes, I use the ImageWriter for windows.
What should I do afterwards?
The next step is to create an unsigned tx (on your online computer) and then send this via a QR code to the offline computer - the "usage.html" details this (got that to appear yet?).
I'm having problems comprehending this part:
Quote
After bitcoins have been sent to the offline generated address to move the "unspent outputs" you will need to
construct one or more "raw transactions".
construct one or more "raw transactions".
Do I first send some change to the address generated via a regular transaction? Then use the offline computer to send the change back again?
What should I do afterwards?
The next step is to send a small amount of BTC to the generated address and then create an unsigned tx (on your online computer) to send it back to yourself and then send this via a QR code to the offline computer - the "usage.html" details this (got that to appear yet?).
If you are still having troubles with usage.html then use: https://github.com/ciyam/safe/blob/master/usage.html (was designed as a
...anyway so just as readable from there).
Okay, I'm done up to the generate new address stage, and all QR codes have been imported to my 'online' computer. I'm downloading kleopatra to verify the keys work. What should I do afterwards?
Jump to: