Quote from: pooler on Today at 10:09:27 AM

Quote from: Architect_of_Time on January 27, 2025, 06:47:52 PM

I've been tuning my L3's recently and I have a few questions I was hoping someone could clear up?

I will only try to answer those questions I'm relatively confident I can answer, as I don't have much hands-on experience with Antminers.

Quote from: Architect_of_Time on January 27, 2025, 06:47:52 PM

1) Are HW errors, rejected/stale shares, etc factored into the reported average hashrate on the miner's status page? In other words, if I have my miner clocked really fast but it's getting way to many HW errors, will it still report a really high hash rate or will it display an "effective" hash rate that is basically all the work done per unit time excluding HW errors?

I believe that HW errors and rejected shares are not factored into the hash rate reported by the miner. So if for example you have a lot of HW errors, the hash rate estimated by the pool will be much lower than the raw one reported by the miner.

Quote from: Architect_of_Time on January 27, 2025, 06:47:52 PM

4) What is the meaning of the Local Work, Utility, and WU fields?

Utility is shares submitted (either accepted or rejected, I believe) per minute. WU or Work Utility is the same thing but counting each share by its difficulty.

Quote from: Architect_of_Time on January 27, 2025, 06:47:52 PM

5) I always assumed the "best share" field is showing what the maximum network difficulty the best share/hash computed by the miner could have been if the miner were to have found a block. In other words, if the best share field read "500,000" then that would be like saying "If the network difficulty were 500,000, the best hash found would have satisfied the requirements to solve/create a new block". But I frequently see the best share field displaying a number substantially greater than actual global network difficulty. Is this because I misunderstand what that field means?

I think you essentially get it. I suspect the problem here is that this "best share" field is expressed as a share difficulty rather than a network difficulty. Due to historical reasons, in the case of coins using the scrypt algorithm, while network difficulty is expressed in the same way as Bitcoin's, share difficulty is expressed on a different scale. For instance, network difficulty 1 corresponds to a share difficulty of about 2¹⁶.

I also am not familiar with Antminer.

1. Typically miners count the number of nonces hashed, whether submitted or not, which would also includes HW errors. I would assume the same unless there is
some indication HW errors are specifically excluded.

5. I assume the same. But I don't see a problem. It's likely you did solve a block but you weren't solo minning so it only counted as another share. Behind the scenes
the block would be created and the accumulated shares distributed to the miners. Best share doesn't really mean anything for pool mining, every share has the same value
based on stratum diff. The different diff factor for scrypt algo should not affect the share diff, it's only used to calculate the target hash associated with the stratum diff.