[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[vickersja]

Here big fat BTCBTCBTC
This block is being a finicky little sucker.
Over an hour since the last block..

These last few weeks have been painful to watch the counter...

This one up to almost 80 minutes.

[DaCryptoRaccoon]

Once the network has had it's re-target it should fall back to the 10m or so blocktimes just with the loss of a fair amount of hashrate has been the main issue here.

Come one blocky where areeeee yhooooo.. 

[jimjam123]

These last 10 blocks or so have taken the most time that i have seen in a super long time...

[vickersja]

100 minutes!?!?!?!?!?!?!?!?!?!?!?!?!?!?!

[chillfactr]

Next block should be a big fat loaded with transactions  block.

[jcriss]

Next block should be a big fat loaded with transactions  block.

yup and I wont be mining it with extra power waiting for BTC to transfer

[willi9974]

We startet our German Bitcoin Lotto Run number 4 —> 10 PH/s for ~1,5 days

Cross Fingers  

[chillfactr]

We startet our German Bitcoin Lotto Run number 4 —> 10 PH/s for ~1,5 days

Cross Fingers  

somebody else pumping about 20Ph also.
which will be alot of help for your group run 

[willi9974]

WTF that was near

   "workername": "1WiLLiPMAVVEd4BxUjmxirHnNDKhBFgWA",
   "hashrate1m": "10.6P",
   "hashrate5m": "9.38P",
   "hashrate1hr": "8.72P",
   "hashrate1d": "5.28P",
   "hashrate7d": "1.31P",
   "lastshare": 1585314319,
   "shares": 426122423576,
   "bestshare": 983.790.572.686
   "bestever": 983790572686

[jimjam123]

Here Blocky...
I see we are going hard the past week+.
Lets get this one Fellas!!!!

[serje]

I hope next time I check this I will see 256

[-ck]

Hi All. Given the change in profile of solo mining, I will be changing the pool shortly to be designed to be optimised for rental and massive miners directly, without the need for a special port. This means the pool itself will be mining with a starting difficulty of 1 million instead of the current 10,000. This will have no effect on your chance of finding a block regardless of how big or small a miner you are, but it does mean that mining statistics for small miners will be unreliable for potentially days on end. It will only be the statistics that will be unreliable; it has no effect on your mining and block finding chances. The reason for doing this is to decrease the resource usage on the pool server and the potential latency for big miners involved with using the special port. All the ports will remain active, but they will all act on the main pool and the regular ports of 3333 and 443 will be the only ones recommended from here on. If you already have a configuration that has been working, you will not need to make any changes. This transition should be transparent for all users. This will involve a pool restart, but as always it should have negligible downtime so there is no need to alter your configurations. The restart will happen within the next hour.

[-ck]

This will involve a pool restart, but as always it should have negligible downtime so there is no need to alter your configurations. The restart will happen within the next hour.

Pool restart is complete. Mine on!

[chillfactr]

This will involve a pool restart, but as always it should have negligible downtime so there is no need to alter your configurations. The restart will happen within the next hour.

Pool restart is complete. Mine on!

did the updates affect the hashrate we had?  i think i saw it at around 15Ph, or more for awhile.
now its at the regular 3 - 4 Ph

or did someones rental just finish 

[-ck]

did the updates affect the hashrate we had?  i think i saw it at around 15Ph, or more for awhile.
now its at the regular 3 - 4 Ph

or did someone's rental just finish 

I had been planning this for some time and waited till I saw the hashrate drop first.

[chillfactr]

did the updates affect the hashrate we had?  i think i saw it at around 15Ph, or more for awhile.
now its at the regular 3 - 4 Ph

or did someone's rental just finish 

I had been planning this for some time and waited till I saw the hashrate drop first.

Ok thank you for the update 

[Fruitman]

hmm sooo after the update my newpac miners with 700ghs are still shown correctly but my 6Th's (2/3 of T9) still show 0ghs ...

[jimjam123]

did the updates affect the hashrate we had?  i think i saw it at around 15Ph, or more for awhile.
now its at the regular 3 - 4 Ph

or did someone's rental just finish 

I had been planning this for some time and waited till I saw the hashrate drop first.

-CK,
Thanks for all of your hard work and commitment to our community.

[DaCryptoRaccoon]

Checked my hashrate on the pool stats and noticed hat they both seem to have failed to submit any shares for some time and both my miners seems to be showing diff 1,000,000 now.

Noticed your post ck my miners don't seem to be able to submit a share at 1M zone been 5 hr since last share was submitted to the pool.

Code:

LSTime
5h 30m 42s ago


{
 "hashrate1m": "0",
 "hashrate5m": "0",
 "hashrate1hr": "25.6G",
 "hashrate1d": "776G",
 "hashrate7d": "849G",
 "lastshare": 1585559889,
 "workers": 2,
 "shares": 23709288026,
 "bestshare": 229508053.8100446,
 "bestever": 36824123071,
 "worker": [

[jimjam123]

Checked my hashrate on the pool stats and noticed hat they both seem to have failed to submit any shares for some time and both my miners seems to be showing diff 1,000,000 now.

Noticed your post ck my miners don't seem to be able to submit a share at 1M zone been 5 hr since last share was submitted to the pool.

Code:

LSTime
5h 30m 42s ago


{
 "hashrate1m": "0",
 "hashrate5m": "0",
 "hashrate1hr": "25.6G",
 "hashrate1d": "776G",
 "hashrate7d": "849G",
 "lastshare": 1585559889,
 "workers": 2,
 "shares": 23709288026,
 "bestshare": 229508053.8100446,
 "bestever": 36824123071,
 "worker": [

Magic,
My S1's and S3's are having similar showings.
They are mining though, just very few hits over the 1M mark. This is expected.
My S9 and S15's are showing up just fine.