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

[Nexus9090]

Is everything running OK on the pools?

I've been looking at the mining stats on one of my OctAxe board for the past couple of days and it just looks like its just mining dirt at the moment.

Returned share values are the lowest I've ever seen, its hardly breaking through 20K 99% of the time highest returned share value over the past 3 days was 18M.

I know random is random and all that but this is not normal.

[-ck]

Is everything running OK on the pools?

I've been looking at the mining stats on one of my OctAxe board for the past couple of days and it just looks like its just mining dirt at the moment.

Returned share values are the lowest I've ever seen, its hardly breaking through 20K 99% of the time highest returned share value over the past 3 days was 18M.

I know random is random and all that but this is not normal.

Except that it is normal.

Everything is running fine.

[buzzard34]

CK, it looks like your certificate just expired on stats.ckpool

[-ck]

CK, it looks like your certificate just expired on stats.ckpool

Thanks, just expired. Should be fixed now.

[buzzard34]

CK, it looks like your certificate just expired on stats.ckpool

Thanks, just expired. Should be fixed now.

Yep, all good now. Thanks.

[Nexus9090]

Is everything running OK on the pools?

I've been looking at the mining stats on one of my OctAxe board for the past couple of days and it just looks like its just mining dirt at the moment.

Returned share values are the lowest I've ever seen, its hardly breaking through 20K 99% of the time highest returned share value over the past 3 days was 18M.

I know random is random and all that but this is not normal.

Except that it is normal.

Everything is running fine.

I'm glad the pool is running OK, but in my experience this flow of low value shares is not normal at all especially over an extended period.

In my experience I've always had gear hitting higher numbers regularly, from a few hundred K to 100's of M was regular even over a short time frame and a few in the 1-10G range was typical over a weeks mining period.

This glut of mining dirt is all barely above share difficulty around 20K and its been going on for a few days now, which is why I questioned it.

So anyway, it is what it is, frustrating at best.

Not that I'll ever find a block, I think those days are gone and come the next halving so will my solo mining adventures.

[o_solo_miner]

CK, it looks like your certificate just expired on stats.ckpool

Thanks, just expired. Should be fixed now.

no acme in use?

[-ck]

CK, it looks like your certificate just expired on stats.ckpool

Thanks, just expired. Should be fixed now.

no acme in use?

I use certbot, but that particular url is behind a reverse proxy which broke the automated update.

[Klinkers]

Ok, i am new to this, i have 2 CYD running here. its showing on the graph as 2 miners running, but its not showing the correct hash. its saying 1 H/s and not the total of 2 x 650Kh/s ish ..

my Bitcoin address is BTCbc1q6w0rer54nrwu3uxqmmew2feq6srtk0vdsr9kya

can anyone help  ?

I am mining to solo.ckpool.org Port 3333

BTC address as user and password x

can anyone help me as to why my stats are not showing properly ?

The workers in numbers is 1 but graph shows 2.

please see this screenshot to show.

https://prnt.sc/XpNiOqWLTux5

[NotFuzzyWarm]

Sorry to say but 650 kHs is a toy miner, probably a CPU miner using the horribly under-powered ESP32 micro controller. They are pretty little things but useless as a BTC miner. You need a miner that is ASIC-based to give AT LEAST several 10's of GHs. The low reported speed is because your miners are not able to process even 1 share during the ~10min between blocks.

Any pool tries to set the miner work difficulty to produce around 18 shares per min. Running at at least 400+ GHs a decent low end ASIC miner such as the original Compac-F will produce at least several hundred valid shares in the same time period. Your 'miners' simply cannot even approach that by using just a cpu.

There only two or three pools in the world that are specifically setup to accept your miners. All the others will reject them because they are far far too slow to contribute anything.

[ABCbits]

and not the total of 2 x 650Kh/s ish ..

can anyone help me as to why my stats are not showing properly ?

If you insist to mine with such low hashrate, i would just recommend you switch to other mining pool. IIRC https://web.public-pool.io/#/ is one of few mining pool that specifically support such low hashrate mining device.

[smallerminer]

To make it easier for people to try stratum v2 by using ckproxy, I've made an installer that automates the download, build, configure, and install of ckproxy on any linux box:

Code:

wget https://api.bitbucket.org/2.0/repositories/ckolivas/ckpool/src/master/scripts/install-ckproxy.sh
chmod +x install-ckproxy.sh
sudo ./install-ckproxy.sh

This should work to any stratum v1 or v2 upstream pool, and not just solo.ckpool.org. Just point your miners to the address of the machine you install the proxy on and your chosen port.

FYI...I tried to consolidate all my miners into 1 stream towards your server using the ckproxy with the -P switch....doesn't seem to like it...tried it with the ckproxy -q -P -c /etc/ckpool/ckproxy.conf, then it fails to launch.  This was in the syslog:  ckproxy.service: Main process exited, code=exited, status-1/FAILURE,  ckproxy.service: Failed with result 'exit-code'.

[-ck]

To make it easier for people to try stratum v2 by using ckproxy, I've made an installer that automates the download, build, configure, and install of ckproxy on any linux box:

Code:

wget https://api.bitbucket.org/2.0/repositories/ckolivas/ckpool/src/master/scripts/install-ckproxy.sh
chmod +x install-ckproxy.sh
sudo ./install-ckproxy.sh

This should work to any stratum v1 or v2 upstream pool, and not just solo.ckpool.org. Just point your miners to the address of the machine you install the proxy on and your chosen port.

FYI...I tried to consolidate all my miners into 1 stream towards your server using the ckproxy with the -P switch....doesn't seem to like it...tried it with the ckproxy -q -P -c /etc/ckpool/ckproxy.conf, then it fails to launch.  This was in the syslog:  ckproxy.service: Main process exited, code=exited, status-1/FAILURE,  ckproxy.service: Failed with result 'exit-code'.

Code:

ckpool -h
-B | --btcsolo
-c CONFIG | --config CONFIG
-D | --daemonise
-g GROUP | --group GROUP
-H | --handover
-h | --help
-k | --killold
-L | --log-shares
-l LOGLEVEL | --loglevel LOGLEVEL
-n NAME | --name NAME
-N | --node
-P | --passthrough
-p | --proxy
-q | --quiet
-R | --redirector
-s SOCKDIR | --sockdir SOCKDIR
-T | --testconfig
-t | --trusted
-u | --userproxy

passthrough is -P
proxy is -p

Case matters

[-ck]

A bugfix and update to be compliant with the latest SV2  spec were applied to all the solo ckpool instances, so they have been restarted. There should have been no discernible miner downtime.