How to merge mining power in one computer

[chinchs]

Hi, anyone knows how to use a single wallet for several rigs? right now I'm using one computer with -server switch and pointing the others to use that computer, but I'm not sure about this, I heard there is a tool called pushpool but don't know how to compile and use it in windows.

[featherman]

you can use existing windows binary, just edit the .conf file (use google to readup) and add server=1, u also add rpc user and password and then use these to connect to coin-qt.exe and mine from it whilst it is running. search for guiminer and minerd

[chinchs]

I'm running the client as a server, and using cgminer, but I'm not sure that all the other clients are mining as one. This is my network

10.0.0.100
Server running litecoin/digitalcoin client as a server
cgminer pointing to 127.0.0.1 with 800 khs/s

10.0.0.101
Client
cgminer pointing to 10.0.0.100 with 1100 khs/s

10.0.0.102
Client
cgminer pointing to 10.0.0.100 with 900 khs/s

Using this configuration, I'm solo mining at 2800 Khs/s?

[The_Catman]

I'm running the client as a server, and using cgminer, but I'm not sure that all the other clients are mining as one. This is my network

10.0.0.100
Server running litecoin/digitalcoin client as a server
cgminer pointing to 127.0.0.1 with 800 khs/s

10.0.0.101
Client
cgminer pointing to 10.0.0.100 with 1100 khs/s

10.0.0.102
Client
cgminer pointing to 10.0.0.100 with 900 khs/s

Using this configuration, I'm solo mining at 2800 Khs/s?

You should probably make sure to set rpcallowip=127.0.0.1 and rpcallowip=10.0.0.* in litecoin/digitalcoin.conf as well, and I think you need to set a port to connect to. Otherwise, I think that sounds right. I've never done much solo mining so I'm not really an expert on it though.

[Stale]

Yeah, this looks correct. Since 10.0.0.101/102 are showing hash rates in CGMiner, they are successfully submitting shares against 10.0.0.100. As such, if any of the machines solves a block, the credit should be reflected in the wallet on the 10.0.0.100 host.

Now sharing an actual wallet against multiple hosts is a different story. I haven't looked into it too much, but generally is not recommended. Simplified, the client software will pre-generate ~100 keys during installation to be used for change transactions, so if you use you're private key from multiple installations it's possible that every installation will 'see' different available balances.

(Though again, I've never looked into this too much)

[chinchs]

Yeah, this looks correct. Since 10.0.0.101/102 are showing hash rates in CGMiner, they are successfully submitting shares against 10.0.0.100. As such, if any of the machines solves a block, the credit should be reflected in the wallet on the 10.0.0.100 host.

Now sharing an actual wallet against multiple hosts is a different story. I haven't looked into it too much, but generally is not recommended. Simplified, the client software will pre-generate ~100 keys during installation to be used for change transactions, so if you use you're private key from multiple installations it's possible that every installation will 'see' different available balances.

(Though again, I've never looked into this too much)

Thanks for the information, I will keep this configuration until a block is found.