I would say take 50% in top shelf coins. BTC, BCH, LTC, BCC Then 25% mid range .25 to $10.00 coins that look stable and that you have looked into what they are about and can see some value in. Like PIVX, LISK, GAME. Then the last 25% in D2G (dust to golds) that you can get a lot (thousands or millio...

URL : prohashing.com:3333/xnsub Worker: nimbus Password: n=1 URL : prohashing.com:3333/xnsub Worker: nimbus Password: n=2 URL : prohashing.com:3333/xnsub Worker: nimbus Password: n=3 URL : prohashing.com:3333/xnsub Worker: nimbus Password: n=4 URL : prohashing.com:3333/xnsub Worker: nimbus Password:...

URL : prohashing.com:3333/xnsub
Worker: nimbus
Password: n=1

example for worker 1 above.

for worker 2 use:
all the same above except:
Password: n=2

etc for each miner

Just put in a difficulty for your hashrate that results in 240-300 shares submitted in 2 hours, about 2.5 shares per minute or less. Ideally the pool would like 120 shares per per 2 hours or 1 share per minute. If you are submitting a share a second, 60 shares per minute or more, your difficulty wil...

I am running some L3+ on PH and recommend that you do not use a static difficulty. Just use n=minername
a difficulty of 16384 is far to low for a L3+ on PH
If you feel you must use a static difficulty then use d=131072 or d=262144

There have been a bunch of ideas thrown around by pool users that are just ideas to treat symptoms as they appear to affect the user themselves while they do not understand that they themselves may be a huge contributor to the problem. The current system limitations are not Hashrate even if that is ...

I am running some L3, L3+ and Titans on the pool. I don't understand the question about withholding blocks. IT looks like things are running good now, but yesterday when the pool was running slow I noticed a lot of Rejected and Stale and restart delays up to 10 seconds. Also a lot of "calculati...

I might say try a clock of 238, 236 as tmopar says, 228 and see which one give you the highest hash at the pool. FYI the X6 was factory undervolted to 1.1 volt and "tuned" to run at 238. I have seen some run at 245, 248 and 250, but most do not. But I have found that each machine has its o...

I am curious if any of the many "balance forfeitures" from "low luck miners" last night were running L3, or L3+.
As far as I can tell on Wednesday July 12th the L3 and L3+ miners were effectively working with 1.25 hashing board disabled, but were paying the power of full hashing.

We are looking a little better today Thursday the 13th. No "Miner is using an incorrect algorithm" that I have seen, but I have not been watching all morning. still getting some "Both primary and merge mined shares are stale 3132 (count)" As I predicted yesterday the pool total i...