This is so cool. I've installed it on my N900 and am up to block 2000. I wonder what the khash/s will be - my guess is 50 khash/s.
Let me know your bitcoin receiving address, and we can make the first p2p (phone-to-phone) transaction.
I created 18T1jQ9QT1fsDJ7q8YKBGhdM56iYt4sXoV on my phone. I'm interested in what the battery hit is like for running it full time. It did take a *long* time to get the block chain. I get between 130 and 150 khash/s when I did a short generation test run. |
|
|
|
I built the needed boost stuff from source, and set BOOST_ROOT.
Now it compiles but the linker crashes.
It's picking up old boost libraries and/or headers. I had this issue too. I hardcoded the makefile to pick the boost stuff I wanted. |
|
|
|
I've updated the first post with the latest release. The "contributed" distribution method should be working now. That is the only substantial change in this release.
Does this require remote miner clients to update as well? Or is it just the server? |
|
|
|
I got bitcoind running on the N900. It wasn't too hard. I had to build the right versions of libdb and libboost and make one minor change to util.cpp. The ParseHex function in util.cpp has code like: 'c' is a 'char' type which is unsigned so this comparison never does what's expected. Changing both instances of this to the following gets a working bitcoind: Where 'working' means it's currently downloading the block chain. I haven't extensively tested it yet. Binary here if anyone wants to risk it: http://bluishcoder.co.nz/bitcoin-pool/bitcoind.gzgunzip it and run it from the terminal. The standard RPC commands will work with it running. Update: 2010-02-04: The changes to ParseHex are no longer needed as they're part of the bitcoin source now. An updated build for the N900 is available here: http://www.bluishcoder.co.nz/bitcoin-pool/bitcoind-b1a657.gzThis is built from github commit b1a657. |
|
|
|
Does that also work for running a server on Windows?
Yes, except replace 'bitcoinr' with 'remoteminer-cpu.exe' or 'remoteminer-cuda.exe'. |
|
|
|
Any ideas?
You should install libboost-all-dev. |
|
|
|
Could someone please provide an example of what command and options I would use to start a mining server?
Also an example of the what client's would have to run to connect to my server.
To run a server on linux: bitcoind -remoteserver -remotebindaddr=0.0.0.0 -remotebindport=8335 -gen Note the 'remotebindaddr'. This is what makes the server accessible over the internet by other clients. To run clients: bitcoinr -server=ip.addr.of.server -address=bitcoinaddress |
|
|
|
|
I added a call to SetLastVerifiedMetaHash but that didn't fix the issue for the contributed distributed type. So I've switched back to 'connected' and this displays the address as being in the pool.
I'll switch back to 'contributed' if the issue is resolved.
|
|
|
|
just be patient and keep reading here, or on the pool-website to upgrade, if needed, as soon as possible.
I fixed what looks like one bug in the best hash verification but it didn't solve this issue. I've switched back to the 'connected' distribution type and that is now printing things correctly. I'll wait till I hear from puddinpop before switching back to contributed and trying to solve the issue. |
|
|
|
|
puddinpop, there appears to be no call to SetLastVerifiedMetaHash in the current code, whereas there is in the last version. Is this a bug?
|
|
|
|
hopefully the "Address ... not found in block solved" thingie doesnt cause any bigger problems
There might be some server up and down-age as I add some debugging to investigate this. Clients should reconnect gracefully. Don't panic if you see it  |
|
|
|
it works, that's a start.
If there were 100 cuda clients in the pool we'd get a block every 5 hours or so. |
|
|
|
It will distribute the coins in the block the same as it did before. If you see the message that the address wasn't found after the client gets its second block, that means something isn't working quite right on the server. Check the bitcoin log file to see if there are any messages about clients failing metahash verification.
There are no failed hashes in the log. But there only seems to be one client passing: If I grep the log for "passed metahash" all I see is one client IP address listed. There are 16 clients connected to the server. |
|
|
|
Me too, not found. Did you switch to contributed and rounding is causing this?
Contributed method is bad imo.
Why is it bad? I asked before switching and the majority of the responses requested contributed. |
|
|
|
cuda-miner does less than half of what i get using m0's (or puddinpops older cuda-versions).
m0's = 45M
remote-cuda= 17M
puddinpop noted to expect this: Also, there is an experimental remote CUDA client included in the release. Expect half the hash rate you get with the regular CUDA miner built into the standard client. |
|
|
|
|
I've noticed this too. I asked puddinpop about it in the other thread.
|
|
|
|
|
puddinpop, when running this latest version I'm always seeing a message on the remote client saying that my address is not found in the block being solved. It doesn't show the share that I'd get that it used to. Is something broken or is there a change in the behaviour?
|
|
|
|
I updated the server on 173.255.205.10 early since there were only 4 clients connected. Instructions updated here: http://www.bluishcoder.co.nz/bitcoin-pool/Basically you need the new client binary. The windows version is now called remoteminer-cpu.exe and the arguments to it require '=' instead of a space between the '-address' and its value (and '-server' and its value). There's also a remoteminer-cuda.exe for those with a cuda compatible GPU. Let see how well this handles load. If it's fine I'll take down the other server. |
|
|
|
|
Show Posts
