|
I guess it's ok for remotely doing it but if your concern is that someone else on the same unix machine can steal your bitcoins this still doesn't help because they can see your command line in /proc, top, ps etc. It could read the password on stdin or use readline or something, to guard against that particular thing at least. Allowing it to be passed on the command line is not good, in my opinion.
Even better might be to use a key file, then you can use unix permissions to make it readable to only that user, kind of like ssh does.. then the bitcoind could have an 'authorized_keys' file with the public keys. Anyway I don't mean to be an ass but the command line thing is just a false sense of security.
|
|
|
|
|
Both, I have a 10.5 and a 10.6 machine both running it. I suspect the problem is the processor. Some of the frameworks and such have a CPUID check in them to prevent them from running on non-intel processors, from what I've heard.
|
|
|
|
|
For low value items like that you would normally accept the transaction without any confirmations. If the bitcoin node that the vending machine is talking to accepted the transaction then it's probably valid. I think the only danger in that is if it was somehow double spent in a short time window - then it may never get into any blocks. I'm not sure if that's really possible, maybe it is, but it seems like it would be hard to pull it off reliably.
|
|
|
|
|
The current bootstrapping mechanisms are working pretty well and we can scale them as demand goes up. If you're unable to connect through IRC or the alternate built in seeding system then you can always use -addnode=1.2.3.4 to specify the address of a running node. Once you have discovered a node and connected you will get the addresses of all the other nodes via the bitcoin protocol and don't need the seeding systems to be able to get on the network. Even if IRC failed you could use one of the addresses from the Static IP Address thread here to connect the first time.
|
|
|
|
|
Try running it with 'bash' instead of 'sh'.. if that doesn't work try to execute the commands one at a time by hand. I just linked em all together with those &&s but I think that's a bash thing.
|
|
|
|
To extend on this you can connect to the remote host and request a new key before you send, as right now that reuses the same address over and over. To connect to the remote server and get an address you could set up pubkey auth with ssh and do something like this : ssh solar@eclipse.heliacal.net bitcoin/bitcoind getnewaddress |
|
|
|
The JSON-RPC interface can be used to query the balance and send it. Try something similar to this.. this will also start bitcoind if it's not running already. You can run this every few hours from cron. #!/bin/bash
NICE=/bin/nice
BITCOIN=/home/solar/bitcoin/bitcoind
ADDR=1XPTgDRhN8RFnzniWCddobD9iKZatrvH4
NODE=192.75.207.66
date
${BITCOIN} getbalance 2>&1 | while read balance;
do
if [ "${balance}" == "0.000000000000000" ];
then
echo "zero balance";
elif [ "${balance}" == "error: couldn't connect to server" ];
then
echo "server not running, starting...";
${NICE} -n 19 ${BITCOIN} -daemon -addnode=${NODE}
else
echo "sending ${balance} BTC to ${ADDR}"
${BITCOIN} sendtoaddress ${ADDR} ${balance};
fi
done
|
|
|
|
|
Still interested in this if anyone has any lenses and such they want to convert to cash/bitcoins.
|
|
|
|
|
Are there any errors maybe in dmesg or the syslog (usually /var/log/messages or /var/log/syslog or something like that)? It's hard to diagnose without seeing it first hand, sorry.
|
|
|
|
Ok I really want to get this right.. sirius-m can you try it one more time? I removed the static link to libgcc which was pulling in the dependency on the newer glibc. I replaced the binaries in this location with new ones : http://heliacal.net/~solar/bitcoin/builds/Linux-amd64-SVN-103/$ ldd bitcoind
linux-vdso.so.1 => (0x00007fff31d9c000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fc6c5b15000)
libm.so.6 => /lib/libm.so.6 (0x00007fc6c5892000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fc6c567a000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007fc6c545d000)
libc.so.6 => /lib/libc.so.6 (0x00007fc6c50da000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc6c5d36000)
|
|
|
|
|
He tried to double spend his coins and the system prevented it. In the process he also lost the coins he didn't spend because he lost one of the wallet files while swapping them around.
It is enough to back up the wallet.dat, try it out with some free coins from the bitcoin faucet.
|
|
|
|
|
I want some nanocomputers!
|
|
|
|
You can do a base only build of wxWidgets - Satoshi is in the process of writing replacement functions for the few hooks that bitcoind still needs from wxWidgets and then it will be possible to do without it completely. Make sure you use wxWidgets 2.9 not 2.8 when you build it. These notes might help you get started, then you can fine tune the configure command from there for your system - http://heliacal.net/~solar/bitcoin/bitcoin-linuxbuild.pdfAlso take a look at the wx-config usage in this makefile: http://heliacal.net/~solar/bitcoin/makefile.unix2 |
|
|
|
|
grep the debug.log file for 'hashmeter'
|
|
|
|
Here is my ldd output for these binaries:
$ ldd bitcoind
linux-vdso.so.1 => (0x00007fffc2dff000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f8433a64000)
libm.so.6 => /lib/libm.so.6 (0x00007f84337e1000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f84335c3000)
libc.so.6 => /lib/libc.so.6 (0x00007f8433240000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8433c85000)
$ ldd bitcoin
linux-vdso.so.1 => (0x00007fff3f5b0000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00007f001d7d4000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00007f001d527000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00007f001d305000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00007f001d0db000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00007f001cebf000)
libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f001cc0b000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00007f001c9c1000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f001c73b000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f001c505000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f001c2bd000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f001c0b9000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007f001beb3000)
librt.so.1 => /lib/librt.so.1 (0x00007f001bcab000)
libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x00007f001b9cd000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00007f001b7c9000)
libSM.so.6 => /usr/lib/libSM.so.6 (0x00007f001b5c0000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f001b3bc000)
libm.so.6 => /lib/libm.so.6 (0x00007f001b138000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f001af1b000)
libc.so.6 => /lib/libc.so.6 (0x00007f001ab98000)
/lib64/ld-linux-x86-64.so.2 (0x00007f001de13000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00007f001a98a000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f001a654000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00007f001a3d1000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f001a1be000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f0019fb4000)
libXi.so.6 => /usr/lib/libXi.so.6 (0x00007f0019da4000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00007f0019b9a000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f0019990000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00007f001978d000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f0019589000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f0019383000)
libz.so.1 => /lib/libz.so.1 (0x00007f001916c000)
libpcre.so.3 => /lib/libpcre.so.3 (0x00007f0018f3d000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00007f0018d24000)
libselinux.so.1 => /lib/libselinux.so.1 (0x00007f0018b05000)
libexpat.so.1 => /lib/libexpat.so.1 (0x00007f00188dc000)
libICE.so.6 => /usr/lib/libICE.so.6 (0x00007f00186c0000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007f00184bb000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f001829e000)
libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00007f0018045000)
libdirectfb-1.2.so.0 => /usr/lib/libdirectfb-1.2.so.0 (0x00007f0017dc2000)
libfusion-1.2.so.0 => /usr/lib/libfusion-1.2.so.0 (0x00007f0017bb7000)
libdirect-1.2.so.0 => /usr/lib/libdirect-1.2.so.0 (0x00007f001799e000)
libpng12.so.0 => /lib/libpng12.so.0 (0x00007f0017777000)
libxcb-render-util.so.0 => /usr/lib/libxcb-render-util.so.0 (0x00007f0017572000)
libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x00007f0017369000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f0017164000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f0016f5e000)
|
|
|
|
|
What kind of computer is it? I only tested on 10.5 with a core 2 duo based mac..
|
|
|
|
|
A 'whole attempt' is actually 3 blocks. 2 blocks of data are hashed to produce a 256 bit result, then that result is padded to make another block and hashed again. Each block is given the usual 64 pass treatment of SHA-256. The interesting part that generates the coins uses a simplified implementation in c++ rather than OpenSSL.
|
|
|
|
|
Show Posts
