It might be a good idea for myself to speak with the members of TX/RX and see about getting an informal BITCOIN NIGHT for non members of TX/RX that is NOT a Friday night.
Thoughts?
I think that is a great idea, I would show up for that. I took some welding classes at TX/RX about a year ago but have never had a chance to get back due to time problems. It is a great place though. It is a great place. I show up on Friday nights when I can. I am not a member but it really is a great place. I emailed one of the members that is interested in Bitcoin about their thoughts. I will keep you in touch. |
|
|
|
|
It might be a good idea for myself to speak with the members of TX/RX and see about getting an informal BITCOIN NIGHT for non members of TX/RX that is NOT a Friday night.
Thoughts?
|
|
|
|
|
Find out which private key the amount is assigned to and export it and import the private key into Mt Gox and then send the amount to your new wallet.
PRESTO!
|
|
|
|
|
So are you saying to buy bitcoin over gold?
|
|
|
|
I'm starting to warm up to this. I apologize if kicking at an open door, but private key can in principle be encrypted, and POS infrastructure could be decrypting it, right? The system could be assymetric and involve public key and denomination as seed/salt...? (Haven't thought this through at all)
It could be, but for this purpose it's not encrypted at all. I actually did make a proposal on the Wiki as to a key/QR code format that is protected with a password. That could be done - in which case you'd hand over the cash and say "the password to my cash is foofoo". I am not sure it would be very practical, because the purpose of printing the cash is to save transaction time, and if the password is long, you waste any time you saved as the cashier types it, and if the password is short, someone who skims the code could crack it, rendering the protection useless. The most practical remedy may be low-tech: cover the spend code with a small post-it note. Password-protected cash also increases the training burden on staff who would be employed to accept it, which makes the deal a little more raw for merchants. The more the bills can function like retail gift cards from the perspective of the clerk, the less often you'll run into clerks who have no clue how to accept them. |
|
|
|
|
Send some to mine. I think I have had 1 donation. Feel free to check.
|
|
|
|
Good read. I wonder if that can happen these days. I should try it. :-D |
|
|
|
|
a very small amount. I do not use an exchange such as Mt Gox as my WALLET if you are asking.
|
|
|
|
I got in during the peak of the bubble last year and then exited and then reentered again as I found out bitcoin was going UP again. Care to donate a few to poor pitiful me to get me up to speed? I will render services in exchange as well.  1MANTisca9kS6t4bngzuU4GBgE1S1L7q2UThank you all! I am long for the long haul now! |
|
|
|
|
Was just thinking since I am so into paper wallets.
Thoughts?
|
|
|
|
Getting this :/ make -f makefile.new bitcoind
g++ -pthread -Wextra -Wno-sign-compare -Wno-char-subscripts -Wno-invalid-offsetof -Wformat-security -g -DNOPCH -I/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src -DUSE_SSL -fno-stack-protector -fstack-protector-all -Wstack-protector -Wl,-z,relro -Wl,-z,now -D_FORTIFY_SOURCE=2 -O2 -I"/home/bitcoin/Bitcoin/Deps/include" -static -o bitcoind obj/checkpoints.o obj/version.o obj/addrman.o obj/netbase.o obj/crypter.o obj/key.o obj/db.o obj/init.o obj/irc.o obj/keystore.o obj/main.o obj/net.o obj/protocol.o obj/bitcoinrpc.o obj/rpcdump.o obj/script.o obj/util.o obj/wallet.o obj/walletdb.o obj/noui.o -Wl,-Bstatic -mtl /home/bitcoin/Bitcoin/Deps/lib/libboost_system.a -mtl /home/bitcoin/Bitcoin/Deps/lib/libboost_filesystem.a -mtl /home/bitcoin/Bitcoin/Deps/lib/libboost_program_options.a -mtl /home/bitcoin/Bitcoin/Deps/lib/libboost_thread.a /home/bitcoin/Bitcoin/Deps/lib/libdb_cxx.a -mtl /home/bitcoin/Bitcoin/Deps/lib/libssl.a -mtl /home/bitcoin/Bitcoin/Deps/lib/libcrypto.a -lgcc -Wl,-Bstatic -l z -l dl -l pthread
/home/bitcoin/Bitcoin/Deps/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_globallookup':
dso_dlfcn.c:(.text+0x30): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
obj/netbase.o: In function `LookupIntern':
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/netbase.cpp:90: warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
obj/bitcoinrpc.o: In function `__static_initialization_and_destruction_0':
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/bitcoinrpc.cpp:2141: undefined reference to `getconnectioncount(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, bool)'
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/bitcoinrpc.cpp:2141: undefined reference to `getpeerinfo(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, bool)'
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/bitcoinrpc.cpp:2141: undefined reference to `listunspent(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, bool)'
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/bitcoinrpc.cpp:2141: undefined reference to `getrawtransaction(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, bool)'
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/bitcoinrpc.cpp:2141: undefined reference to `createrawtransaction(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, bool)'
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/bitcoinrpc.cpp:2141: undefined reference to `decoderawtransaction(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, bool)'
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/bitcoinrpc.cpp:2141: undefined reference to `signrawtransaction(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, bool)'
/home/bitcoin/Bitcoin/Libraries/bitcoin-master/src/bitcoinrpc.cpp:2141: undefined reference to `sendrawtransaction(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > > const&, bool)'
collect2: ld returned 1 exit status
make: *** [bitcoind] Error 1 you don't have all the dependencies installed, you need to install glibc and try again My suggestion is to not run bitcoind and to rely on a web wallet that has API calls similar to bitcoind such as blockchain.info https://blockchain.info/json_rpc_api1MANTisca9kS6t4bngzuU4GBgE1S1L7q2UTHAT IS EVEN WORST THAN RUNNING AN UNSECURED BITCOIND I was presenting simple solution. This isn't an UNSECURED method either. Why does it need to be CentOS and not something simpler such as Ubuntu? |
|
|
|
My suggestion is to not run bitcoind and to rely on a web wallet that has API calls similar to bitcoind such as blockchain.info https://blockchain.info/json_rpc_api1MANTisca9kS6t4bngzuU4GBgE1S1L7q2U |
|
|
|
I wonder if judge.me is capable of setting up wills and keeping my super secret password safe until I die.
Do you want the crypto nerd answer? Timelock encryption http://www.gwern.net/Self-decrypting%20filesEncrypt the private key using a timelock encryption algorithm so that it will take roughly 10 years to solve with a single processor (timelock algorithms are designed to make parallel processing impossible). Then as long as you are alive just move the funds every 5 years and publish a new timelock encryption problem. Make the timelock algorithm and encrypted key part of your will and when you die your heir can get the funds in 10 years by simply solving the latest problem. * It doesn't have to be 10 years. Smaller is possible but requires more frequent changes and if there is a computing revolution or cryptographic flaw it gives you less time to move funds. I like this idea! |
|
|
|
Thanks for the votes of confidence  Surely a year without any security issues counts for something? Just giving you a heads up on the target not necessarily any vulnerabilities. Please take our votes as a word of CAUTION. We like you! |
|
|
|
Of course, an electronics destroying solar flare could pose a problem.
You can always keep a copy of the blockchain on a VHS tape. They can store up to ~4.5GB (usually around 3.5GB). Ummmm Electro MAGNETICPulse |
|
|
|
|
Show Posts
