nrpeyton
commented
2 years ago Closed this myself.
I fixed the problem myself. (It was caused by my core clock being too high (not memory), but core clocks.
I didn't think it could be the cause because the rejection reason was not [invalid], and in the Miner the invalid share count for each GPU was showing in the column where stale (expired) shares normally sits.
Strangely, this has also drastically improved my pool-side efficiency, I'm getting over 100 now for both dual altogythms, which is an average increase for ethereum too, which never even had an issue. (Or I never knew I had one).
Issue closed.
Hi guys
I am Dual Mining Ethereum + TON.
On Ethereum, I get:
But for TON: (primarily tcp.whalestonpool.com {stratum}, but did try {HTTPS} too at server1.whalestonpool.com).
Some things I've noticed:
--The rejection reason is always rejected: seed, my [expired] and [invalid] are both always zero.
--I googled the reason [rejected: seed]? but could not find a description? If it's useful, my latency is good, 40ms to 65ms depending on how I measure it.
--gminer 2.85 does not communicate with tcp.whalestonpool.com (stratum), or server1.whalestonpool.com (HTTPS) as often as it communicates with my Ethereum pool (us1.ethermine.com). For example, for every packet sent/received from tcp.whalestonpool.com, 10x times as many packets have been sent/received with us1.ethermine.com (measured with wireshark packet capturing).
--I have included a portion of my log.txt, (including copy/pasted config file to top). high rejected shares & low pool-side efficiency - whales.txt