Topic: Ethermine.org increased stale after fork (Read 571 times)

Also started getting stale shares today. Had to switch my WiFi adapter to wire. For me, it seems that the ping makes a lot of difference now. Using NanoPool.

Dwarfpool shows diff 2000MH instead ethmine 4000MH, I've noticed stales increase too, I'll try dwarf for now

The same goes for me, although I have to admit that the estimated earnings improved considerably. On average, I have 3%-6% stale and 0% invalid. How I know ethermine will not pay you for stale. For the moment, I would not change anything as long as my estimated earnings parameter is up.

Hi I have same issue I have 2-7% stale and I am pretty sure they dont pay you nothing for stale shares. It sucks I am thinking about switching pool because with those stale shares I lose about 5% more than before fork on same pool.

I don't only get high stale share but also low effective (current) hashrate (reported 182 MHs, current ~140 150). Are you guys experiencing the same on current hashrate?

I have the same issue.
Does ethermine pay stale shares? Nanopool says it pays for stale shares if they could produce an uncle.  Unfortunately, nanopool doesn't show the stale/reject shares statistic.

Actually Nanopool has the highest share diff set at 5000MH (4000MH for ethermine, been like this for a long time).
I'm almost sure it's because of a combination of low block time and fluctuating ping. Does anyone know what the upper limit of an efficient ping time is?

I believe the problem is they increased their share difficulty before the fork to help reduce their server load. This was fine back then as blocks normally took 25-35 seconds to be found, so even with a high share difficulty even a modest rig could sent a share or two before new work from a new block was issued. Now after the fork with block times down to, or even under, 15 seconds the higher share difficulty means an increased chance that you may not find a valid share in the time in takes the network to find a new block.

Normally this poses no problem and the pool issues you new work which your client starts crunching on. But now with the lowered block times the chances of you finding a share and submitting within that short window of time when the work is valid and the pool issues new work due to a new block being found is also increased, meaning basically there is now an increased chance for submitting stale shares. This is probably more true for those with smaller rigs and lower hashrate users as they would be the ones to be more likely to not submit work, or submit late work, during the now shorter block time windows. The higher hashrate users submit stales too, but this is dwarfed by their valid submission rate, thus it looks like it is not effecting them, although it is, just to a smaller extent.

I believe Ethermine has a higher share difficulty than most other pools, thus why it is more noticeable with their pool than others. About the only thing you can do is submit a ticket to them and have them look into it. If enough users complain they might do something about it.

Hi, i believe im not the only one with this issue, usually before fork i have 1~3% stale, after the fork now im getting 7~11%
thats pretty much a lot
so far tested
1) ping is stable as it was before
2) swapped between US1 US2 EU1 EU2 servers
3) gpu downclock

Usually i see top miners with huge hashrate +20 GH/s getting only 1% max 2% stale