Better to mine multiple machines with same wallet or not in same pool or not?
-
@haitch said in Better to mine multiple machines with same wallet or not in same pool or not?:
@rds Your passphrase is not sent while pool mining, only while solo mining does it get sent to the wallet server. In pool mining the pool pass-phrase is sent to the wallet server.
I hear you, but when I have to supply the passphrase, I'd rather it be an account that is not holding much on average. I remember a scenario awhile back where the Bitcoin core wallet when mining had a small window where the passphrase was accessible and some mining accounts were hacked, a few had many bitcoin in them and they were lost.
-
@xburst said in Better to mine multiple machines with same wallet or not in same pool or not?:
@haitch & @ZapbuzZ - much appreciated info - hopefully useful to others down the line! I am waiting on a USB3 hub so for now most are trying to work via USB2.0 - I know that will increase the overall read times as I had been using up all the available USB3 sockets earlier.
USB 3.0 over 2.0 will increase read times by 5-8 times.
-
I did a tiny test the other night as far as mining two different wallets on two different machines in the same pool. One laptop with 1.2tb plots and one laptop with a 64g plot.
- Both miners would start up fine but after that first block would pass neither miner would start back up for the next blocks. Everything just stalled. Re tried and re tried same result each time.
I was wandering if this was because both miners are coming from the same IP address?
- Each time network quality would start at 100% but shortly after startup would dwindle down to less than 50% on both machines. With one machine I'm usually at 100% network quality.
Could this be my internet connection? Think I'm on 10 megs..Or again IP addresses? One laptop was on wifi the other Ethernet cable.
-
Right now trying one wallet, two machines, one pool. 1.2tb on one and 800g on the other.
- Getting tons of SENDER: can't connetct. Error: 10060
- Network quality slowing on the down trend. About 8 blocks in one machine down to 74% the other is at 42%.
- Miners are starting slow. Last miner to submit on each block so far.
- Annnnnd now its frozen again. The block chain is 2 blocks ahead.
Looks like one machine is the best I'll be able to do. Might try each machine in a different pool tomorrow.
-
This post is deleted!
-
You must have network issues. I run one machine solo with 3 local wallets running at the same time pointed to 3 different ports, 127.0.0.1:8105, 8115 and 8125. I run a second machine solo with 2 local wallets pointed to 8105 and 8125. All 5 miners are scanning the same Burst account.
I also run this same configuration on Burst.Ninja. 3 miners pointed to the pool on one machine and 2 miners pointed to the pool on the other. It can be done, you have to figure out what is going on with your network. I had local wallet syncing issues for awhile I thought about pulling my hair out but I got them resolved over time. When I shut down a wallet that is showing up to current block, I copy the 2 files in the db folder to a backup folder so if in the future one wallet forks or gets stuck I load the known good backup db and get it going again. I haven't had to do that in a few weeks though.
When solo mining I monitor Burst.Ninja on a web browser to see if my miners are on the right block. Burst.Ninja is by far the most reliable pool in the system, IMO.
-
@rds Very fricking interesting. I never thought of more than one wallet from one machine. Can't really fathom how that would work.
-
@Dillion , it works well. If one wallet gets stuck I only loose 1/5 of my mining capacity.