SASEUL mining REJECTED going up? What 'Stale share' and 'Timestamp out of range' mean

· Setup

SASEUL mining REJECTED: what do these English messages mean?

Most are shares that arrived late. Only check your connection and clock when they pile up

Stale share

The job already moved on · 84% of rejections

Timestamp out of range

The time is out of range · 10%

timed out

The pool didn't answer in time · 4%

Share of each reason the pool refused a share, counted from a mining program log (miner.log) from one graphics card, August 18 to October 9, 2026. Other connection errors make up about 1.5%.

'Stale share' means that while a share (proof of work you hand to the pool) was being found, the pool's job moved on to the next round. 'Timestamp out of range' means the time written on the share you sent was outside the range the pool accepts.

In a log from one graphics card run from August 18 to October 9, 84% of rejections were Stale share. That's about 200 to 470 a day, against 6,000 to 7,000-something accepted shares a day. Roughly 3 to 7 out of every 100.

That's the kind of rejection you get naturally. The only thing to do is check your internet, your computer's clock, and the pool's status, in that order, when the rejection rate suddenly goes up.

You can see the rejection rate from two numbers on the Mine tab and from the log file

At the bottom of the mining program's Mine tab you'll see ACCEPTED (shares the pool took) and REJECTED (shares it turned down). Divide REJECTED by the sum of the two and you have the rejection rate. For example, 950 accepted and 50 rejected is 5%.

Bottom of the Mine tab in the SASEUL miner. Hashrate, ACCEPTED shares and REJECTED shares fields, numbers hidden
The bottom of the SASEUL mining program's Mine tab (screen from September 15, 2026). You work out the rejection rate from ACCEPTED and REJECTED. I've hidden the exact numbers.

The screen doesn't tell you why a share was rejected. But the mining program keeps a log (a file where it writes down what it did). The file is called miner.log. The answers the pool (a group that mines together and splits the coins) sends back are written there as-is.

How to read the log in the command-line version

These are commands from the mining program's help.

miner.exe status
miner.exe log

You'll see lines like this mixed in. The accepted and rejected at the end mean the same as the two numbers on the Mine tab.

hashrate: 703.92 MH/s (gpu 50%, ... accepted 583, rejected 43)

There were four reasons for rejection, and eight in ten were Stale share

I counted the reasons the pool refused shares across more than 7 weeks of logs. September 23-24 and 28 are missing because the program wasn't running those days.

Why the pool refused shares (August 18 to October 9, 2026)

  • Stale share409 Conflict 17,464times
  • Timestamp out of range400 Bad Request 2,170times
  • read operation timed outTimeout 873times
  • Other connection errorsgetaddrinfo failed, etc. 319times
Count of the pool's answers written in a SASEUL mining program log (miner.log) from one graphics card. 20,826 in total.

A Stale share is an exam paper handed in late, and most of them are normal

Here's what the pool sends back:

Stale share: the round moved on while this one was being mined.

It means the pool's job moved on to the next round while the share was being found.

It's like handing in your exam after the bell. Even if your answers are right, the papers have already been collected, so it doesn't count.

In this log, Stale shares stayed about the same the whole time, 200 to 470 a day. If they come in steadily like that, it's fair to see them as a normal part of mining rather than a broken connection. My guess is they go up if you're far from the pool or your internet is slow.

Timestamp out of range means the time is outside the range, and I don't know why it happened

The original message is "Timestamp out of range." It means the time written on the share was outside the range the pool accepts.

The log alone can't tell me why. In September it happened 20 to 60 times a day, but in early October it went up to 80 to 120 a day. Timeouts went up around the same time too, but I don't know if the two are connected.

If your computer's clock is wrong, the times can be off, so it's worth checking the clock. That doesn't mean the clock was the cause in this log.

도표 JSON 오류 (note): Unexpected token 'C', "Checking t"... is not valid JSON

Timeouts went up from October, so look at your internet and the pool

"The read operation timed out" is a timeout. It means the pool didn't answer in time when sending a share or getting a new job. Through September it was 0 to 26 times a day, but from October 1 it went up to 41 to 164 a day. October 3 was the highest at 164.

If your internet is fine and these lines still go up, it may be something on the pool's side. Among the other connection errors, getaddrinfo failed means the computer couldn't look up the internet address, so usually you check your internet connection first.

You can't compare work by the number of shares alone

In my earlier post on what shares mean, I wrote that the pool splits rewards by the ratio of accepted shares. Looking more closely at the same log, there's a part that the share count alone can't explain.

In August, when the graphics card was set to use only 25%, the average hashrate for a day was about 180 to 315 MH/s. From September, after raising it to 50%, it was about 740 to 890 MH/s. The speed differed by more than 3 times, but accepted shares per day were similar: 6,300 to 7,200 in August and 7,300 to 7,500 in September.

The log has a "difficulty adjusted to …" line for each share. It looks like the pool changes the share difficulty (how high the bar is for one share to count) for each miner (a guess). Then a fast card sends fewer shares at a higher bar, and a slow card sends more at a lower bar.

The pool's own guide also doesn't say by count. It says "Split by the work each address did". So my guess is that the actual split is by amount of work including difficulty, not by number of shares. On October 9, the payout waiting box on the pool's front page also showed an amount of work, "164 T", separately next to the share count (9,668 shares). The screen doesn't explain what unit T is exactly.

So what should you do? Measure the rate, and only chase the lines that went up

  1. On the Mine tab, work out REJECTED ÷ (ACCEPTED + REJECTED). If it's about 3 to 7 out of 100, you can leave it alone
  2. If it's mostly Stale share, check whether your internet is slow or dropping. If you're on Wi-Fi, it's worth trying a wired connection
  3. If Timestamp out of range suddenly goes up, check that Windows 'Set time automatically' is on
  4. If timeouts go up, see whether the pool site's (saseulmine.com) front page opens. You can ask whether others are seeing the same thing through the Telegram menu at the top of the site
  5. Don't compare yourself to others by share count. Check the coins you actually got for your address on the official explorer.

If you want to go back over setup, see the Windows install screens post. SASEUL's basic numbers are on the SASEUL basics page.

Sources


I hold SL. I counted the rejections from the mining program log for August 18 to October 9, 2026. I opened and checked the pool's guide and Microsoft's help page myself on October 9.

Questions after reading this

Leave a question you want answered. Useful ones are added to this post with an answer. Please do not include your name, contact details, wallet address or recovery phrase.