The current version of the Bitcoin software should indeed assign different work to each of your mining nodes (via he getwork JSON RPC) call.
However...
1.5Ghash may not be enough for an effective solo operation, especially these days. You'd earn a few coins a day I'd imagine from a pool with that rig though.
Topic: avoid redundancy, solo mining with 4 machines (Read 805 times)
I would like an answer to this as well. I'd assume all machines are assigned a unique hash.. but confirmation is needed.
bump
Hey guys, so I set myself up to run solo. I used guiminer to launch the bitcoin client in server mode and set up a username and password. My question is:
I have 3 different machines and 1 username and password that they all connect with. Does the server divide up the possible hashes so that each machine is working with a unique hash?
It would be pointless to have all 3 machines working on the same hash. I know that with pools you have to use a different worker with each miner, but I found no way to make "workers" when soloing.
Thanks,
Jeff
I'm soloing at about 1.5 Gh/s
I have 3 different machines and 1 username and password that they all connect with. Does the server divide up the possible hashes so that each machine is working with a unique hash?
It would be pointless to have all 3 machines working on the same hash. I know that with pools you have to use a different worker with each miner, but I found no way to make "workers" when soloing.
Thanks,
Jeff
I'm soloing at about 1.5 Gh/s
Jump to: