Quote from: nizzuu on August 14, 2017, 06:40:40 AM

Hi there. Joblo, thanx for your great work. Can u please check the possible issue? The problem is hashrate reporting while solo mining (getwork):

********** cpuminer-opt 3.6.8 ***********

[2017-08-14 09:29:31] Binding process to cpu mask f
[2017-08-14 09:29:31] Binding thread 0 to cpu mask f
[2017-08-14 09:29:31] Binding thread 1 to cpu mask f
[2017-08-14 09:29:31] Binding thread 2 to cpu mask f
[2017-08-14 09:29:31] Binding thread 3 to cpu mask f
[2017-08-14 09:29:31] 4 miner threads started, using 'cryptonight' algorithm
[2017-08-14 09:29:32] Current block is 19325
[2017-08-14 09:29:32] No payout address provided, switching to getwork

Then it may take about 10+ minutes to display hashrate, or even up to 1 hour (the result will be printed for all that time though). Tried several coins and several algos, as well as sse42 and avx/avx2 versions, and the previous 3.6.7 version. No changes there. I personally do not see some walls to avoid hasrate output, as all built-in-wallet miners do that. This reproduces both on win7 and win10.

It's hard to tune settings (I'm not about cryptonote algo, of course) for new coins with such a wait Undecided

I had to use shitpool with zero miners and broken payouts to tune Grin

Cos on stratum work there's no issues.

I use some kinda stock .conf file, which is similar for all the coins.

Maybe there're some solutions rather than miner's code? Thanks.

I'm not sure I understand the problem. It is normal to have fewer hash reports when solo mining because you have to solve
the entire block, not just a share.