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

[-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.

[vickersja]

Interesting. My lonely GekkoScience NewPac is showing fine.  Or is it the Antminer portal that is showing incorrect?  The stats page on solo.ckpool.org are working for me.

Terminus Pod 606 is arriving today and will be placed on the solo pool.

 "hashrate1m": "40.5G",
 "hashrate5m": "43.4G",
 "hashrate1hr": "40.7G",
 "hashrate1d": "55.8G",
 "hashrate7d": "425G",
 "lastshare": 1585583480,
 "workers": 1,
 "shares": 447328718,
 "bestshare": 430277908.3557194,
 "bestever": 2443683507,

I had a few more running hence my 7d hashrate.

[DaCryptoRaccoon]

Took one S3+ 1h 15m to submit a 1 Million share bit of a pain trying to monitor the miners now can't tell if they are down by looking at the hashrate on the pool anymore as it's fluctuating depending on share submissions now.

Not able to use the pool stats now to monitor the hashrate's as they keep going to 0 until they submit a share which is a pain for keeping track of them when away from them.

Code:

{
 "hashrate1m": "20.7G",
 "hashrate5m": "932G",
 "hashrate1hr": "1.02T",
 "hashrate1d": "755G",
 "hashrate7d": "843G",
 "lastshare": 1585594269,
 "workers": 2,
 "shares": 23712440129,
 "bestshare": 229508053.8100446,
 "bestever": 36824123071,
 "worker": [
  {
   "workername": "",
   "hashrate1m": "0",
   "hashrate5m": "0",
   "hashrate1hr": "77.3M",
   "hashrate1d": "283G",
   "hashrate7d": "388G",
   "lastshare": 1585559889,
   "shares": 1880326927,
   "bestshare": 229508053.8100446,
   "bestever": 2336012756
  },
  {
   "workername": "",
   "hashrate1m": "20.7G",
   "hashrate5m": "932G",
   "hashrate1hr": "1.02T",
   "hashrate1d": "472G",
   "hashrate7d": "458G",
   "lastshare": 1585594269,
   "shares": 19581629978,
   "bestshare": 81953418.32696119,
   "bestever": 36824123071
  }
 ]
}

[philipma1957]

a 1 board s7ln works okay


http://solo.ckpool.org/users/146UJM5kgzLVUV23CXCf33KQKHckoX1gx3


{
 "hashrate1m": "1.12T",
 "hashrate5m": "1.18T",
 "hashrate1hr": "1.19T",
 "hashrate1d": "1.04T",
 "hashrate7d": "575G",
 "lastshare": 1585596678,
 "workers": 1,
 "shares": 27203547953,
 "bestshare": 169463142.0658723,
 "bestever": 13461125718,
 "worker": [
  {
   "workername": "146UJM5kgzLVUV23CXCf33KQKHckoX1gx3",
   "hashrate1m": "1.12T",
   "hashrate5m": "1.18T",
   "hashrate1hr": "1.19T",
   "hashrate1d": "1.04T",
   "hashrate7d": "575G",
   "lastshare": 1585596678,
   "shares": 27171378329,
   "bestshare": 169463142.0658723,
   "bestever": 13461125718
  }
 ]
}

[-ck]

Leave them running a few days and they should show the correct hashrate. This sure is gonna be a pain to support...

[os2sam]

Leave them running a few days and they should show the correct hashrate. This sure is gonna be a pain to support...

So the share difficulty will eventually adjust down?

If that is so will the pool still honor the "--suggest-diff" argument?

I, for one, like this change.

[-ck]

Leave them running a few days and they should show the correct hashrate. This sure is gonna be a pain to support...

So the share difficulty will eventually adjust down?

If that is so will the pool still honor the "--suggest-diff" argument?

I, for one, like this change.

Yes the share diff will adjust down, and suggest-diff still works. The minimum share diff is still 1, it's just that the start diff is 1M because of the amount of rentals hitting the pool now. The proxy feeding the 1M share diffs before was consuming too many resources and adding some latency which was unacceptable as a long term solution. Additionally workernames were being stripped previously whereas now the full workernames work.

[mikeywith]

A single S9 14th shows.

{
 "hashrate1m": "19.4T",
 "hashrate5m": "15T",
 "hashrate1hr": "13.4T",
 "hashrate1d": "13.7T",
 "hashrate7d": "14.1T",
 "lastshare": 1585628545,
 "workers": 1,
 "shares": 60239023864,
 "bestshare": 1698973146.6154,
 "bestever": 14867475388,
 "worker": [
  {

Everything seems fine so far, obviously smaller gears might have an issue with the hashrate shown on the pool for a while but that was a good step, either way, makes renting hash power a bit easier to deal with.

Thanks for keeping us updated -ck.

[willi9974]

Hello all,

i startet our 5. Bitcoin Lotto Run in Germany.
but, did NiceHash has a problem after the pool update?
I startet 4 orders one on the US and one on the EU markt, but both were killed by nicehash.

1. rental: solo.ckpool.org:4334 --> terminated
2. rental: de.ckpool.org:4334 --> terminated
3. rental: solo.ckpool.org:443 --> terminated

now i have startet the 4. one on de.ckpool.org:443

It is the same with the last one.

- first i get 10 PH/s was i have orderd, status "active"
- speed goes down, status switched to "not active"
- all miner are disconnected and the status switched to "canceld"

Any help....?


Update: i startet a other one on port 3333 --> we will see...

Update2: the last order on US server 3333 is also dead.

Update3: other on on the EU server on port 3333 also dead.


On the picture you can see, some miner bridges from my nicehash retal going to "diff to low" and after that, the complete rental was canceld and dead.






@-CK, can you have an eye on it?


Best Regards from germany
Willi

[-ck]

Hello all,

i startet our 5. Bitcoin Lotto Run in Germany.
but, did NiceHash has a problem after the pool update?
I startet 4 orders one on the US and one on the EU markt, but both were killed by nicehash.

1. rental: solo.ckpool.org:4334 --> terminated
2. rental: de.ckpool.org:4334 --> terminated
3. rental: solo.ckpool.org:443 --> terminated

now i have startet the 4. one on de.ckpool.org:443

It is the same with the last one.

- first i get 10 PH/s was i have orderd, status "active"
- speed goes down, status switched to "not active"
- all miner are disconnected and the status switched to "canceld"

Any help....?


Update: i startet a other one on port 3333 --> we will see...

Update2: the last order on US server 3333 is also dead.

Update3: other on on the EU server on port 3333 also dead.


On the picture you can see, some miner bridges from my nicehash retal going to "diff to low" and after that, the complete rental was canceld and dead.






@-CK, can you have an eye on it?


Best Regards from germany
Willi

That's insane. Not only does fuckingshithash demand a 1 million starting diff, it also demands a 1 million minimum diff? The hashrate it's contributing isn't even enough to sustain 1 million diff which is why the pool is lowering the diff so... Oh well forget it, there's no point complaining, they're not going to fix that shit now. Perhaps I need to go back to the old way. Let me think about it.

[willi9974]

yes i'm with you, i don't understand it with NiceHash, but NiceHash is in that game the biggest player.
If you can downgrade your pool to latest version, it could be a fast workaround or see you a other solution?

Best Regards from germany
Willi

[-ck]

yes i'm with you, i don't understand it with NiceHash, but NiceHash is in that game the biggest player.
If you can downgrade your pool to latest version, it could be a fast workaround or see you a other solution?

Best Regards from germany
Willi

I can go back to the way it was. Without writing special code for it, the only other option is to make the pool's minimum diff 1 million and that's just not on. I'll roll it back tomorrow.