Pages:
Author

Topic: [ANN] CIYAM Safe - offline tx's using QR codes for comms - page 3. (Read 6144 times)

legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
Is there still a spot open for the reward?

Yup - still 8 BTC remaining (in the title of the OP) and only one other member working on it at the moment. Smiley
member
Activity: 84
Merit: 10
Is there still a spot open for the reward?
legendary
Activity: 1792
Merit: 1111


Here you can see the transaction record: http://blockchain.info/address/1ELPYyJKLfeQHPu3FCSSKfFHjhCkEbapct

For the reward please send to 1CiZPrEJdN4FJcqdLdgVLzT8tgCXxT5ion

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


It's well received. Thank you!
legendary
Activity: 1792
Merit: 1111
Well, I'm giving up for the night before I break more stuff. The ./signtx script does not return anything now after I mistyped the password the first time. I've restarted everything to no avail.  Undecided
Damn, I found the problem.  The signtx script was corrupted.  Undecided Now how should I go around to fix this ?
 No text editor, no internet connection for apt-get commands....

Use vi for editing
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
Here you can see the transaction record: http://blockchain.info/address/1ELPYyJKLfeQHPu3FCSSKfFHjhCkEbapct

For the reward please send to 1CiZPrEJdN4FJcqdLdgVLzT8tgCXxT5ion

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

Damn, I found the problem.  The signtx script was corrupted.  Undecided Now how should I go around to fix this ?
 No text editor, no internet connection for apt-get commands....

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. Smiley
legendary
Activity: 1288
Merit: 1227
Away on an extended break
Well, I'm giving up for the night before I break more stuff. The ./signtx script does not return anything now after I mistyped the password the first time. I've restarted everything to no avail.  Undecided
Damn, I found the problem.  The signtx script was corrupted.  Undecided Now how should I go around to fix this ?
 No text editor, no internet connection for apt-get commands....
legendary
Activity: 1288
Merit: 1227
Away on an extended break
Well, I'm giving up for the night before I break more stuff. The ./signtx script does not return anything now after I mistyped the password the first time. I've restarted everything to no avail.  Undecided
legendary
Activity: 1792
Merit: 1111
Finally I copied the rawtx to the offline computer by an USB drive

Here you can see the transaction record: http://blockchain.info/address/1ELPYyJKLfeQHPu3FCSSKfFHjhCkEbapct

For the reward please send to 1CiZPrEJdN4FJcqdLdgVLzT8tgCXxT5ion

Thanks!

--------------------------------------------------------------


1) the GPG public key for "local"
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.19 (GNU/Linux)

mQGiBFDpmwQRBACzhWy0y0yzsbA9KW2D168EI8rZS8Qrv2W5AJcf6NgZ/d1wG5/i
4ALaLqWebnf79ObsWOqQGhXE1FxwTUlsQg/j00bBZKYZxVeKClAsC/ytST0JgVE2
lZlMT+Jiter3l8ag1YMZcjNbJwXJyx6l2RBhrGca44HviAzgcPUTWtn+SwCglwf4
jE1sWH7Bee2WwOwAym0MLxED/0jbGZC6M9I57i17Bocpzr62YXvddLVxzubDtV1s
G0ebowdpo3qqhXW8r+seoicIvtPLxTxcIDKKtCUQ21t70MVE+c7BlGX1EhxSLLMi
woaxgUzA3Ouykl+OgrT2+k98azQc5wRm+FpCRp/y+htqKl7x3Xk2Lncvr3Rq8qaW
B8RZBACAOQj6GqAzpRCzQJ0qznv91IjTWdpptAZA8h7ivAG/sCpEJ7Zu6KVOCx+Z
DamPLdhkoWf8ERI8Bxo+6MMyap84+BPwTf3ZvHwW7Exo4ls43TRtqE5DnETaKWJW
YgmAK4rK5tO/gB6U5KJAP1gvyz/0w29qhf/8ESgKX0iT8AAjJ7QfbG9jYWwgaGVs
cGVyIDxsb2NhbEBkb21haW4ubmV0PohjBBMRAgAjBQJQ6ZsEAhsjBwsJCAcDAgEG
FQgCCQoLBBYCAwECHgECF4AACgkQdqqlQ8mt3+J64ACeNZ/BjXncwcKstID7/F+2
u28i2eYAn26XMtJyVMuSpXp7AZzSUnWiN+qZuQENBFDpmwQQBACKX1h/5UtXRW81
EHeVEkVQYzEcaPN2lKnOBRm8kdyP7TMbgSTenKO0iQChyt7TKJUghyB82U7eASoJ
BFsjC7pAMkdrvji1ZE8HAoOtNXJpCUUvdUz/z4oXqu3vBG8RjSuBjtdornczyFpT
bFcHRblUMNkLOpYeStvubHIXGRSAowADBgP/SlZnKmxufK+WGf24B7t6lCq2iHyz
4GvrVBdBI0X4+rlpbtuR4UqaDCIHfmEwgASoxcxPex7VUszl1CWJt8EripuiyHJZ
cItydxxG8bbb4xdhNPU6CtlHFcSQmXq0rDExslZbsKp3SmVQxGUuVvzTxCPGs2/O
CjiI0FNRJNqZA5mISQQYEQIACQUCUOmbBAIbDAAKCRB2qqVDya3f4g5qAJ0XQ07u
vE/pZVMtvEo0nH/LxH0jZQCbBTOsEnd+oNbAHX1o1xl90eDF5C0=
=Wc7N
-----END PGP PUBLIC KEY BLOCK-----


2) both the GPG public key and encrypted private key for "tux"

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v2.0.19 (GNU/Linux)

mQGiBFDpmiwRBACTf1252QYuTZeJ3MrUnc6jiP9DUwgC6g2gcM/LU7toUNJJ5Y6t
AHniBi6VRIPlCQ9qJILBkK9OG2SCKToj+lMdludXKvcyvNhEC4nsjnqDem+h43lC
miUX+5fh9CDq2fiEawDxbxKmlCb5WYUX340NKEQX5g51kCJrqAMC+8UZwwCglma6
4dzVrMf4RlZpsobYGw9vghED/jQlcIc5RgMNJYbOyZrI4qrW0B9ao7Q9hKWFGYw/
U5IbSAoOoj15tx4sCUOIo9hmdMiBHK3kGT+KRqnNitjviwXNsKu4lAYqGRtaL3mB
KbOciwkeCusl1+YFDGEEgPyqg/1AlvETY8zFpSEAiDscCg5GPGahAu5w3HHau4gL
91tsA/9SPcl2/RnXx8zTWOnnr9rs5t1i/UvY8ftQ3I6DA5uVIt6jU7iaJa/M4blP
T6r7PtV3/vcco6nzhyPjLWcsPzLzEjlfKBqqV3+HDxY3PVQSk6kNfqvHLfrCgKc5
PD2Oodkf6ZGxLVRMUtQYQKDdNXeT8L6AMYmJ8YXBYdjAf4ZzbbQbdHV4IG1hc3Rl
ciA8dHV4QGRvbWFpbi5uZXQ+iGMEExECACMFAlDpmiwCGyMHCwkIBwMCAQYVCAIJ
CgsEFgIDAQIeAQIXgAAKCRAq4HIYbk6gaPSwAJ9gVKTWUFakyomFawenMb5zcG9a
aACfc1kd4WJcJI88jbI/O15leKrmAN25AQ0EUOmaLBAEALh4WdpzSmhZqpHQ/IMw
Hu/6BAswtdkA1FOWvuvi758mGjFefburrTSqiqQAW19DPTi8lOetdy7fo3sWJJxn
7g2+F/jXtMTI0ssQTct9W2HjpojkLS3mHj0lCjHqLufHQAQA9unHd32GJ3b6vsRE
9EBW3rXDYnnvXgtaz5H7xYsvAAQLA/4rUhEKjVVx+9/kF/Cbzn4SQ5Lroe9G1pOx
Hn68qF5vPgGItrO3kHM9cpLE/OO7s/3jM3XeQ1EyeI5rom35md8m43biSB2qmOvt
MEueVTntVqrfhmky+N9CG6YK2jKwP/kMp+kEt/CCFOBYKXdwSjLAccfL4Scumghc
cpYRmjYaj4hJBBgRAgAJBQJQ6ZosAhsMAAoJECrgchhuTqBog6YAnROi0tQ65hPz
S8UhFAUdeUG/bo/RAJ4u49DiZAzI7UkgMs7DFkv5QZoEIQ==
=eQOL
-----END PGP PUBLIC KEY BLOCK-----

-----BEGIN PGP PRIVATE KEY BLOCK-----
Version: GnuPG v2.0.19 (GNU/Linux)

lQHhBFDpmiwRBACTf1252QYuTZeJ3MrUnc6jiP9DUwgC6g2gcM/LU7toUNJJ5Y6t
AHniBi6VRIPlCQ9qJILBkK9OG2SCKToj+lMdludXKvcyvNhEC4nsjnqDem+h43lC
miUX+5fh9CDq2fiEawDxbxKmlCb5WYUX340NKEQX5g51kCJrqAMC+8UZwwCglma6
4dzVrMf4RlZpsobYGw9vghED/jQlcIc5RgMNJYbOyZrI4qrW0B9ao7Q9hKWFGYw/
U5IbSAoOoj15tx4sCUOIo9hmdMiBHK3kGT+KRqnNitjviwXNsKu4lAYqGRtaL3mB
KbOciwkeCusl1+YFDGEEgPyqg/1AlvETY8zFpSEAiDscCg5GPGahAu5w3HHau4gL
91tsA/9SPcl2/RnXx8zTWOnnr9rs5t1i/UvY8ftQ3I6DA5uVIt6jU7iaJa/M4blP
T6r7PtV3/vcco6nzhyPjLWcsPzLzEjlfKBqqV3+HDxY3PVQSk6kNfqvHLfrCgKc5
PD2Oodkf6ZGxLVRMUtQYQKDdNXeT8L6AMYmJ8YXBYdjAf4Zzbf4DAwIsn8J6ft4F
qrKN7yWJGO4FM/V78HfaRQOhvo/GRusvF1VAifm8f8GTpdFHVhjJzJ9vCIzrYdE9
6+BSPLQbdHV4IG1hc3RlciA8dHV4QGRvbWFpbi5uZXQ+iGMEExECACMFAlDpmiwC
GyMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRAq4HIYbk6gaPSwAJ9gVKTW
UFakyomFawenMb5zcG9aaACfc1kd4WJcJI88jbI/O15leKrmAN2dAVgEUOmaLBAE
ALh4WdpzSmhZqpHQ/IMwHu/6BAswtdkA1FOWvuvi758mGjFefburrTSqiqQAW19D
PTi8lOetdy7fo3sWJJxn7g2+F/jXtMTI0ssQTct9
W2HjpojkLS3mHj0lCjHqLufH
QAQA9unHd32GJ3b6vsRE9EBW3rXDYnnvXgtaz5H7xYsvAAQLA/4rUhEKjVVx+9/k
F/Cbzn4SQ5Lroe9G1pOxHn68qF5vPgGItrO3kHM9cpLE/OO7s/3jM3XeQ1EyeI5r
om35md8m43biSB2qmOvtMEueVTntVqrfhmky+N9CG6YK2jKwP/kMp+kEt/CCFOBY
KXdwSjLAccfL4ScumghccpYRmjYaj/4DAwIsn8J6ft4FqrKg0zacZhOh/SetqdSE
4aywkN091wkm5Svqd9m/Blk3Sy0CIooAcG7Nlk4fu+ks2Z0/E9tqiDMkh+742iyX
TohJBBgRAgAJBQJQ6ZosAhsMAAoJECrgchhuTqBog6YAnReo03ya140ys/NgTEsT
ozt9HOV0AJ47vYxgLNJX4jqhD6YKhvZeOtSVDw==
=/U/N
-----END PGP PRIVATE KEY BLOCK-----


3) the User Key and Password that were used (neither must be *blank* and be sure not to use anything you would ever normally use elsewhere), and finally

User Key: aaa
Password: bbb

(no space before or after)


4) the GPG encrypted private key for the "offline signed" tx

-----BEGIN PGP MESSAGE-----
Version: GnuPG v2.0.19 (GNU/Linux)

hQEOA3+eMCSari/1EAP/SclHGmHEHVWYYE4uN1GEMffqlOhJ+xR8+JfzR7eK2alU
uu8pRPfqWGHpQHdPhoWdVrxBee/1m5S48vn1DYig1hAfgu/IPDlH7geuql70AefV
/m9iPpxY5O/YjoNe+oZqVm181SDEE8z9+S08gDDogR9VLuMZ/Vht1yn8fpNkrqQE
AJrgNOvwE1XfFvlF2G1a2Tbrxb9pXDYjEQiYCzP9Z/ouBw3/9ziYb+wdj2faTx+w
p0EdQNAjpc4WXcT3XcZJPcJFumfkx5VXPLrlqkoyCzy6FiuZJ4zZ2hGEQlrD+Rbu
8zo28qsGcKhNhrt7qQL54BGLV6/IXf01dAl7huvXzhxj0sAKAUX7rjERO74w4NBH
5mEC9mxFdyUtdZQUCuCKWWSkqyi74+VyUhXRskMVC4s5x0qWz2ynAFZGGWeQPHJl
OlqCSmOu7sNKYaFe2HFeR8kdLb2PqJo54sSDixtf1mNrcZ8QJ7+U3EPQwQIvbvD+
IGNW9PExnz83HRgr1An6QrWhI7S0kPS+e+hjD9IV+ZDDnjMi4/y4xBfcEoLh3Ksa
IbIF/ATAoCKRyO0XtAtF/v8G/nAWvQ6wLoEBvUNAgK52X7pRcVhz1dBsjBB8SQ==
=f01G
-----END PGP MESSAGE-----
legendary
Activity: 1792
Merit: 1111
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.


It works after I reflash the USB key

However, the webcam on my netbook (the offline computer) is not working. How can I move the raw transaction back to the offline computer?
legendary
Activity: 1288
Merit: 1227
Away on an extended break
PS: Do I need to issue this command in the online PC or offline PC?

Quote
createrawtransaction "[{\"txid\":\"62f04f8ee14567ef9a052a56cbda2f7489ccdf17177658a728108c50d4f5c250\",\"vout\
":1}]" "{\"1PutTheAddressToSendToInHerexxxxx\":0.099}]"

I'm guessing on the online PC though...
legendary
Activity: 1288
Merit: 1227
Away on an extended break
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.

Okay. I'll try to poke around with it at the meantime.
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
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.
legendary
Activity: 1288
Merit: 1227
Away on an extended break
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.
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
Can see John's tx now (he's half-way there).

Smiley
BCB
vip
Activity: 1078
Merit: 1002
BCJ
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!
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
What size is required for the USB drive?

I think that 16 GB is required (although maybe this could be changed).
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
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.
BCB
vip
Activity: 1078
Merit: 1002
BCJ
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?
legendary
Activity: 1288
Merit: 1227
Away on an extended break
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.
legendary
Activity: 1890
Merit: 1086
Ian Knowles - CIYAM Lead Developer
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).
Pages:
Jump to: