Solo mining (by creating my own pool of systems)

[stex2009]

I have a couple of machines with GPU's/CPUs. I want to mine solo but don't want to create multiple wallets on each system. Instead would like to consolidate all the blocks I earn into one wallet.
Is there a quick way do this or does this require a lot of effort and is not worth. Anyone has experience with the same?

[Voodah]

You can set up a p2pool.

But honestly, don't do it, solo mining will get you nowhere with current diff unless you have lots and lots of GH/s.

You're better off using a pool.

[Trillium]

Work out your total Mh/s (hopefully many Gh/s if you intend to solo mine...) and use one of the many profitability calculators to work out how long it will take you on average to find a block (it will almost certainly be many months or years) and if this is acceptable to you then you can solo mine. But realistically you're better off with a pool as Voodah says.

[stex2009]

You can set up a p2pool.

Is it simple? Will investigate more now.

But honestly, don't do it, solo mining will get you nowhere with current diff unless you have lots and lots of GH/s.

I don't want to solo mine BTC or LTC. I am solo mining junk ones for now. I mainly want to test this.

[ISAWHIM]

You use one wallet, and mine off that, with all your miners...

You create a config file like this, where the wallet.dat is found.
(In the "Roaming" folder. EG: "C:\Users\YourUserLoginName\AppData\Roaming\Junkcoin")

FILE NAME: junkcoin.conf (Just a standard txt file renamed to what the miner calls itself, or expects to find, or you tell it to use.)

CONTENTS OF FILE: ###############################

splash=0
server=1
gen=0
testnet=0
daemon=1
maxconnections=100
listen=1

rpcuser=YourLoginNameForMiners
rpcpassword=SomeHardToGuessPassword
rpcallowip=*
rpcport=5555

################################# END OF FILE (Do not add this line)

The rpc port is how you connect... The IP for your wallet will be http://127.0.0.1:5555 for the miners on the same machine as the wallet. For the other miners on your HOME NETWORK... you will have to find your network address IP that your router gives the machine with the wallet.

EG, Looking at my wifi settings, I see my IP for this machine is like this...

NETWORK CONNECTION DETAILS:
IPv4 Address: 192.123.0.7

Eg, another computer on the home network may be 192.123.0.3... 4....5....6 etc... You want them all to connect to this one, with the wallet. The wallet will give them all work, and they will mine as one large machine. All depositing into that ONE wallet.

[stex2009]

so, on the machine which has wallet installed I currently use localhost:<port>
This works perfectly for me (I also have a config file in roaming dir).

I did't get how to get other systems on my network to use the same wallet. Do I need a config file on each machine? Should I be using localhost:<port>, same as the main machine (where wallet is installed?)

[Winterfrost]

Localhost just refers the computer to itself; you want to use the IP address of the machine running the wallet, i.e. the network address assigned by your router. It's usually something like 192.168.1.XYZ. Use that as the server and 5555 as the port. Assuming you're on Windows, you can find the IP address by going to Network and Sharing Center -> Local Ara Connection -> Details... -> IPv4 Address.

Example:
There are two machines, M1 and M2. M1 hosts the wallet and M2 is just another miner. The IP address assigned to M1 is 192.168.1.112.
One M1, you use localhost:5555 in the mining software to connect to the wallet. On M2, you use 192.168.112:5555 in the mining software.

[stex2009]

Localhost just refers the computer to itself; you want to use the IP address of the machine running the wallet, i.e. the network address assigned by your router. It's usually something like 192.168.1.XYZ. Use that as the server and 5555 as the port. Assuming you're on Windows, you can find the IP address by going to Network and Sharing Center -> Local Ara Connection -> Details... -> IPv4 Address.

Example:
There are two machines, M1 and M2. M1 hosts the wallet and M2 is just another miner. The IP address assigned to M1 is 192.168.1.112.
One M1, you use localhost:5555 in the mining software to connect to the wallet. On M2, you use 192.168.112:5555 in the mining software.

perfect! Will try this now!

[Timelord2067]

Many thanks for posting this information - just a quick follow up question, does the 'host' box then mine with a pool, or run solo?

[stex2009]

Example:
There are two machines, M1 and M2. M1 hosts the wallet and M2 is just another miner. The IP address assigned to M1 is 192.168.1.112.
One M1, you use localhost:5555 in the mining software to connect to the wallet. On M2, you use 192.168.112:5555 in the mining software.

I am using the same on the other system now:
<ip address of wallet computer M1>:<same port number from M1>

But, this is not working! Anything else I need to check? I dont need to create a config file on M2?

[Winterfrost]

Many thanks for posting this information - just a quick follow up question, does the 'host' box then mine with a pool, or run solo?

In this setup, it's mining against the daemon for the coin (Bitcoin, Litecoin, etc.) so it's running solo.

I am using the same on the other system now:
<ip address of wallet computer M1>:<same port number from M1>

But, this is not working! Anything else I need to check? I dont need to create a config file on M2?

Is it having problems connecting? Try making sure there's no firewall blocking incoming connections on that port. You could also try forwarding that port in your router to be extra sure. You'll need to configure the mining software, but you only need to configure the wallet daemon on the one machine.

[stex2009]

Is it having problems connecting? Try making sure there's no firewall blocking incoming connections on that port. You could also try forwarding that port in your router to be extra sure. You'll need to configure the mining software, but you only need to configure the wallet daemon on the one machine.

I get this, looks like connection issues:

[2013-07-01 15:54:07] 16 miner threads started, using 'scrypt' algorithm.
[2013-07-01 15:54:38] HTTP request failed: Operation timed out after 30015 milliseconds with 0 bytes received
[2013-07-01 15:54:38] json_rpc_call failed, retry after 30 seconds