Quote from: -ck on Today at 11:13:25 AM

Quote from: DaCryptoRaccoon on Today at 10:44:33 AM

Quote from: -ck on June 05, 2025, 03:25:14 AM

Quote from: DaCryptoRaccoon on June 04, 2025, 11:48:33 PM

Why has his best share not re-set?

Soon as a block is found my one starts again but this one still says his best share is the one that found the block? Undecided

Trivial bug I guess, holding the share value across the share reset code.

I think there is a issue CK.

I now have 2 miners and 1 of my own saying there best shares are not showing on the pool.

I can share one of mine is not showing the correct best share.

Code:

"hashrate1m": "317G",
   "hashrate5m": "407G",
   "hashrate1hr": "424G",
   "hashrate1d": "3.08T",
   "hashrate7d": "57.7T",
   "lastshare": 1749206175,
   "shares": 674105907778,
   "bestshare": 10270859.78562477,
   "bestever": 544020438532
  },

Defo missing the best share

Code:

{
"hashrate1m": "1.39T",
"hashrate5m": "1.33T",
"hashrate1hr": "1.3T",
"hashrate1d": "8.23T",
"hashrate7d": "146T",
"lastshare": 1749206715,
"workers": 3,
"shares": 1627182286323,
"bestshare": 226914168.3892226,
"bestever": 735463252605,
"authorised": 1710841905,
"worker": [

Best share is not the same as shown in the miners.
Also can't think of any reason why one miners best share after a block find would not reset and others best shares are not being reported.
If needed I have more images and this is not just a issue for me another miner who is mining on the pool has the same missing best share.

Did you change something on the pool?
The fact is it's not just 1 issue here or just 1 person its multiple issues and not the same people which leads me to think pool issuse.

https://solo.ckpool.org/users/bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374

Defo not right that the block finders best share didn't reset everyone elses did and now we have multiple users claiming there best shares are not being reported.

Please have a dig CK something is wrong.

Best Regards!

This is what I get clicking on your link. Is this the block solver's?
{
"hashrate1m": "0",
"hashrate5m": "0",
"hashrate1hr": "1.03K",
"hashrate1d": "8.92P",
"hashrate7d": "7.55P",
"lastshare": 1749097721,
"workers": 0,
"shares": 7820993228871,
"bestshare": 137427866914851.2,
"bestever": 137427866914851,
"authorised": 1721981103,
"worker": [
  {
   "workername": "bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374.4",
   "hashrate1m": "0",
   "hashrate5m": "0",
   "hashrate1hr": "1.03K",
   "hashrate1d": "8.92P",
   "hashrate7d": "7.55P",
   "lastshare": 1749097721,
   "shares": 5674287510091,
   "bestshare": 137427866914851.2,
   "bestever": 137427866914851
  }
]
}

The pool code is unchanged for... well years, and as you can see it's been running for 193 days.

As for why the block solver's share might not have changed, that share is being "processed" as a block at the same time the share are being reset so it's easy for its value to behave different to everyone else's due to a race with parallel code.

As for yours, the "best ever" is 735G, much higher than your photo. I guess you got better at some stage? Or are you referring to the best share? I don't know your timeframes here; when you got the best ever on the hardware, and when the pool found the last block.