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

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

[willi9974]

thanks for your support -ck !!!

[DaCryptoRaccoon]

Ahhh bliss back to 401 diff   Don't think the S3's liked 1M one of them was trying for over 12 hr's until it found one.

Thanks for the roll back CK

[-ck]

I'll be restarting the pool shortly with some updates, with the 4334 port to return as a highdiff port, set to 1 million. Downtime should be minimal. Additionally, as I'd been planning for a while with the halving, the fee will unfortunately be increased to 2%.

[-ck]

I'll be restarting the pool shortly with some updates, with the 4334 port to return as a highdiff port, set to 1 million. Downtime should be minimal. Additionally, as I'd been planning for a while with the halving, the fee will unfortunately be increased to 2%.

Restart complete, along with the upgrades and a built-in high diff port that supports workername extensions and adds no latency or overhead to the pool. Miners who wish to try a rental please try it out.

[-ck]

In the unlikely event someone is on mainland china ONLY and wishes to mine solo, I've added two links to a passthrough to the solo pool:

Code:

cnsolo.ckpool.org:3333
cnsolo.ckpool.org:4334 For high diff/low bandwidth mining

[willi9974]

NiceHash is not working
I tried all ports (443,3333,4334)

PoolCheck from NiceHash side

Pool verification process is complete. Tested pool is incompatible!

Pool host solo.ckpool.org resolved to IP 45.59.68.74... OK
Connecting to Stratum proxy for region: USA... OK
Selected mining algorithm: SHA256... OK
Sending mining subscribe request... OK
Sending login information... OK
Mining subscribe request successfully completed... OK
Received mining set difficulty... OK
Received mining set difficulty... OK
Pool difficulty too low (provided=10000, minimum=500000)... Error

[-ck]

NiceHash is not working
I tried all ports (443,3333,4334)

PoolCheck from NiceHash side

Pool verification process is complete. Tested pool is incompatible!

Pool host solo.ckpool.org resolved to IP 45.59.68.74... OK
Connecting to Stratum proxy for region: USA... OK
Selected mining algorithm: SHA256... OK
Sending mining subscribe request... OK
Sending login information... OK
Mining subscribe request successfully completed... OK
Received mining set difficulty... OK
Received mining set difficulty... OK
Pool difficulty too low (provided=10000, minimum=500000)... Error

Okay thanks. The pool switches within 1 second to 1 million diff, but it appears to not even recognise that. That means I'll have to change the minimum diff across the pool to 500k as well. Will restart it shortly with that change. I apologise to all the smaller miners for doing this, but rentals are by far the bulk of the hashes hitting the pool now.

[-ck]

Okay thanks. The pool switches within 1 second to 1 million diff, but it appears to not even recognise that. That means I'll have to change the minimum diff across the pool to 500k as well. Will restart it shortly with that change. I apologise to all the smaller miners for doing this, but rentals are by far the bulk of the hashes hitting the pool now.

Configuration updated, please try again.

[willi9974]

thanks -ck

the NiseHash Pool Test reports now all green!
I will start a 10PH/s rental in the next minutes

Best regards from germany
Willi


Update:
The NiceHash Rental is startet now

   "workername": "1WiLLi3BUxWL2EkD569Gk4udrRs69PUds",
   "hashrate1m": "8.98P",
   "hashrate5m": "2.56P",
   "hashrate1hr": "234T",
   "hashrate1d": "118T",
   "hashrate7d": "33.7T",
   "lastshare": 1585721250,
   "shares": 5351000000,
   "bestshare": 11237120512.31431,
   "bestever": 11237120512