[∞ YH] US/EU/AU solo.ckpool.org 2% fee solo mining 311 blocks solved!

[-ck]

Sadly they didn't find a block and got with in a bee's dick with that one share.

I've updated the stats pages for http://solo.ckpool.org and http://eusolo.ckpool.org to display SI unit prefixes.

[Nexus9090]

Sadly they didn't find a block and got with in a bee's dick with that one share.

I've updated the stats pages for http://solo.ckpool.org and http://eusolo.ckpool.org to display SI unit prefixes.

Wow all that hash rate and they didn't break the diff barrier, so close. That must be really frustrating for them, I think I'd be in tears! 

What hope does a measly 6TH/s have against a monster like that.?!?

[buzzard34]

Sadly they didn't find a block and got with in a bee's dick with that one share.

I've updated the stats pages for http://solo.ckpool.org and http://eusolo.ckpool.org to display SI unit prefixes.

Wow all that hash rate and they didn't break the diff barrier, so close. That must be really frustrating for them, I think I'd be in tears! 

What hope does a measly 6TH/s have against a monster like that.?!?

Double frustrating for them given that two days earlier that would have been a block.

[Nexus9090]

-SNIP-
Double frustrating for them given that two days earlier that would have been a block.

Indeed, quite unreal.

The diff now at an all time high and the global hashrate pushing close to 1 Zetta hash.

The odds for small solo miners diminishes substantially at each retarget

Mind boggling to say the least.

[Andrey123]

Hello friends!
Where else can I find a list of solo pools?
My worker is displayed on the pool, but I doubt that everything is ok.

I don't know about solo pools anymore.

[chrysophylax]

-SNIP-
Double frustrating for them given that two days earlier that would have been a block.

Indeed, quite unreal.

The diff now at an all time high and the global hashrate pushing close to 1 Zetta hash.

The odds for small solo miners diminishes substantially at each retarget

Mind boggling to say the least.

Well ...

We should setup our own and stay with it - not just rent hash.

Follow through with a set number of people joining in as one group and keep it hashing. So every little Moner will be for the Greater Group HashRate.

#crysx #cwi

[Nexus9090]

Well ...

We should setup our own and stay with it - not just rent hash.

Follow through with a set number of people joining in as one group and keep it hashing. So every little Moner will be for the Greater Group HashRate.

#crysx #cwi

The problem I have with that is by the time you've got enough hashrate within a group, the split on the winnings isn't big enough to make it interesting and it would have been better off hashing to PPLNS.

The winnings just get too diluted. I'd be massively frustrated should I join a group then my little rig is the one to turn up the win and end up having to split with 60 other people.

Each to their own but for me solo, means solo.

[chrysophylax]

Well ...

We should setup our own and stay with it - not just rent hash.

Follow through with a set number of people joining in as one group and keep it hashing. So every little Moner will be for the Greater Group HashRate.

#crysx #cwi

The problem I have with that is by the time you've got enough hashrate within a group, the split on the winnings isn't big enough to make it interesting and it would have been better off hashing to PPLNS.

The winnings just get too diluted. I'd be massively frustrated should I join a group then my little rig is the one to turn up the win and end up having to split with 60 other people.

Each to their own but for me solo, means solo.

Maybe ...

Though Greed has never driven Me nor has Money - but what You say does make sense.

I guess it is yet to be seen whether a very large HashRate is better and more proficient (no matter how small the part of reward - as long as there are many) to solve more blocks than trying for one for most of the SoloMiners here.

It would be good to be able to at least see it all in action.

#crysx #cwi

[Nexus9090]

-SNIP-
Maybe ...

Though Greed has never driven Me nor has Money - but what You say does make sense.

I guess it is yet to be seen whether a very large HashRate is better and more proficient (no matter how small the part of reward - as long as there are many) to solve more blocks than trying for one for most of the SoloMiners here.

It would be good to be able to at least see it all in action.

#crysx #cwi

You know @Willi9974 runs a group pool running on solo.ckpool

https://bitcointalk.org/index.php?topic=5478927.0

So you can see a group in action, I believe it has over 100 members already; though sadly they've yet to find a block as far as I know. I wish them continued good luck with their venture.

There's no question over a large hashrate having better success, its basic mathematics in that respect. More hash rate increases the odds of finding a hash that results in a block.

For solo miners home miners the odds diminish each retarget and the retargets rarely go down and when they do its only a few percent change. So for your average 500GH-1TH solo miner the odds are really stacked against you. Gone are the days of switching on a solo miner for a few days and getting a block.

Its getting to the point where solo mining is being pushed into the 10's of TH/s in order to be in with even a remote chance.

Thats not to say lower hash rate miners cant find a block, its just being pushed so far away with each retarget.

Random being what it is there's always a possibility even with the slowest of miners.

[-ck]

Congratulations to miner bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374 who recently ramped up hashrate for solving the 300th block solved at http://solo.ckpool.org!

Code:

[2025-06-04 23:18:25.680] Possible block solve diff 137427866914851.187500 !
[2025-06-04 23:18:25.742] BLOCK ACCEPTED!
[2025-06-04 23:18:25.745] Solved and confirmed block 899826 by bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374.4
[2025-06-04 23:18:25.745] User bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374:{"hashrate1m": "261P", "hashrate5m": "259P", "hashrate1hr": "154P", "hashrate1d": "16.1P", "hashrate7d": "6.11P", "shares": 7368138157895, "authorised": 1721981103}
[2025-06-04 23:18:25.745] Worker bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374.4:{"hashrate1m": "261P", "hashrate5m": "259P", "hashrate1hr": "154P", "hashrate1d": "16.1P", "hashrate7d": "6.11P"}
[2025-06-04 23:18:25.822] Block solved after 217015107377796 shares at 170.9% diff

https://mempool.space/block/000000000000000000020c5281e68cbf5b382e02e3a42d4a9d2965b08d1f8bb3

[DaCryptoRaccoon]

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? 

Code:

{
 "hashrate1m": "255P",
 "hashrate5m": "238P",
 "hashrate1hr": "185P",
 "hashrate1d": "20.2P",
 "hashrate7d": "6.72P",
 "lastshare": 1749080658,
 "workers": 380,
 "shares": 7456392485743,
 "bestshare": 137427866914851.2,
 "bestever": 137427866914851,
 "authorised": 1721981103,
 "worker": [
  {
   "workername": "bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374.4",
   "hashrate1m": "255P",
   "hashrate5m": "238P",
   "hashrate1hr": "185P",
   "hashrate1d": "20.2P",
   "hashrate7d": "6.72P",
   "lastshare": 1749080658,
   "shares": 5309686766963,
   "bestshare": 137427866914851.2,
   "bestever": 137427866914851
  }
 ]
}

[-ck]

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? 

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

[ethanhunt2023]

Congratulations to the miner and the pool for the 300th block.

[Nexus9090]

Congratulations to miner bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374 who recently ramped up hashrate for solving the 300th block solved at http://solo.ckpool.org!

Code:

[2025-06-04 23:18:25.680] Possible block solve diff 137427866914851.187500 !
[2025-06-04 23:18:25.742] BLOCK ACCEPTED!
[2025-06-04 23:18:25.745] Solved and confirmed block 899826 by bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374.4
[2025-06-04 23:18:25.745] User bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374:{"hashrate1m": "261P", "hashrate5m": "259P", "hashrate1hr": "154P", "hashrate1d": "16.1P", "hashrate7d": "6.11P", "shares": 7368138157895, "authorised": 1721981103}
[2025-06-04 23:18:25.745] Worker bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374.4:{"hashrate1m": "261P", "hashrate5m": "259P", "hashrate1hr": "154P", "hashrate1d": "16.1P", "hashrate7d": "6.11P"}
[2025-06-04 23:18:25.822] Block solved after 217015107377796 shares at 170.9% diff

https://mempool.space/block/000000000000000000020c5281e68cbf5b382e02e3a42d4a9d2965b08d1f8bb3

Congratulations to -ck and the miner

261PH solo mining!?   

No wonder they won a block, a 1 in 3137 chance of finding a block at that hash rate. an average of 1 every 22 days.

Congrats!!

[-ck]

Congratulations to miner bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374 who recently ramped up hashrate for solving the 300th block solved at http://solo.ckpool.org!

Code:

[2025-06-04 23:18:25.680] Possible block solve diff 137427866914851.187500 !
[2025-06-04 23:18:25.742] BLOCK ACCEPTED!
[2025-06-04 23:18:25.745] Solved and confirmed block 899826 by bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374.4
[2025-06-04 23:18:25.745] User bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374:{"hashrate1m": "261P", "hashrate5m": "259P", "hashrate1hr": "154P", "hashrate1d": "16.1P", "hashrate7d": "6.11P", "shares": 7368138157895, "authorised": 1721981103}
[2025-06-04 23:18:25.745] Worker bc1qa8r4up9nchkvdnhcf9feexv2jfantrk48ef374.4:{"hashrate1m": "261P", "hashrate5m": "259P", "hashrate1hr": "154P", "hashrate1d": "16.1P", "hashrate7d": "6.11P"}
[2025-06-04 23:18:25.822] Block solved after 217015107377796 shares at 170.9% diff

https://mempool.space/block/000000000000000000020c5281e68cbf5b382e02e3a42d4a9d2965b08d1f8bb3

Congratulations to -ck and the miner

261PH solo mining!?   

No wonder they won a block, a 1 in 3137 chance of finding a block at that hash rate. an average of 1 every 22 days.

Congrats!!

Looks like they only recently started a rental at that hashrate, even though they'd been mining here with a lot less hashrate for some time. But they did get extremely lucky as they weren't mining for long at all at that hashrate.

[Nexus9090]

-SNIP-
Looks like they only recently started a rental at that hashrate, even though they'd been mining here with a lot less hashrate for some time. But they did get extremely lucky as they weren't mining for long at all at that hashrate.

That's quite a rental 260PH.

Most I've ever rented was 2PH. That didn't exactly go well, it done worse than my own 6TH rig running along side it.

But, I guess random is random and luck favours the brave.

[DaCryptoRaccoon]

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?  

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!

[-ck]

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?  

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.

[DaCryptoRaccoon]

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

Missing a best share on here.

Should be 600m like the image.


   "bestshare": 10270859.78562477, 

Never have I seen missing best shares before or best shares sticking. 

   "workername": "bc1qtesc50ye5euqtr67sdqke8xdwef6klasc5vx59.Satoshi",
   "hashrate1m": "456G",
   "hashrate5m": "440G",
   "hashrate1hr": "425G",
   "hashrate1d": "3T",
   "hashrate7d": "57.4T",
   "lastshare": 1749208579,
   "shares": 674106145912,
   "bestshare": 10270859.78562477,
   "bestever": 544020438532

[-ck]

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?  

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.