Yes I agree with you, invalid / stale share will definitely exist, but the ratio of their number to the number of Accept share is important.
In the previous test in 8 hours there was about 0.2% reject / invalid in hiveos, at the same time in the pool it was about 4%.
But now it is much more stable in the 2miners pool.
I’ve used hiveon in the past, and my stale share was usually less than 2%. But apparently there is a problem now and the hiveon pool is increasing the number of invalid / stale shares.
Surely you know that the return displayed in hiveos is not what is in the pool, because when a share is sent to the pool, it takes time to reach the pool, which is ping. At this time, hiveos displays that share as Accept, but in the same short period of a few milliseconds that it took to send the share to the pool, the other share may be stale, in which case the share in the pool is displayed as a stale share. Is given and displays the same share in hiveos Accept share.
But our problem is not stale share at all. The problem now is invalid share.
As you know, invalid shares is a share whose difficulty is less than the difficulty determined by the pool and that share becomes invalid. This is a hardware error.
I guess you do not understand some of my sentences, I apologize because English is not my language.
im very sorry