@ -ck
where is the ckproxy discussion at?
i redid my linux system and need to readup
a little bit on that topic
it used to be in your sig but not anymore
The link is on the solo homepage, but here it is again: https://bitbucket.org/ckolivas/ckpool |
|
|
|
I've added a redirection to the stats provided by our gracious user @bedla at http://solostats.ckpool.orgI'd love to host the stats page on the pool itself but unfortunately bedla hasn't offered to provide the code so for the time being you'll have to be redirected to his setup. I'll probably be dicking with the secondary IP today to make http to https redirect work properly. Long term I will be removing port 443 mining, as it appears to not be helping anyone and making the website unnecessarily complex. |
|
|
|
People have asked me how long the miner who solved the block has been mining for. I don't know exactly since their hashrate may have fluctuated over that time. However, assuming they always mined to the same address, they currently have 2486021304645 shares. Dividing that by the current difficulty of 13732352106018.34 that means he found the block at about 18% diff, so in less than 1/5th of the expected time for the current diff. If they've been mining with a stable 70TH all along, they've been mining for a very long time here.
It was not always 70 Th) sometimes there was a rental of about 1PH. I figured as much. Ah so it was you. Your previous message was a little cryptic. block solved)
Thanks)
Congratulations  There was no need to reveal yourself, but I'm sure you'll be happy to be congratulated. |
|
|
|
|
People have asked me how long the miner who solved the block has been mining for. I don't know exactly since their hashrate may have fluctuated over that time. However, assuming they always mined to the same address, they currently have 2486021304645 shares. Dividing that by the current difficulty of 13732352106018.34 that means he found the block at about 18% diff, so in less than 1/5th of the expected time for the current diff. If they've been mining with a stable 70TH all along, they've been mining for a very long time here.
|
|
|
|
|
Funnily enough, with this block solve, I've finally found out why the pool's best share counter lags behind after a block solve. It only increments with a user's "bestever". It's a harmless cosmetic problem only, but will be addressed in the next pool restart whenever that happens. There are no outstanding bugs or issues so I don't really see much point in restarting it for such a cosmetic issue. The only reason I might consider restarting it is to provide an extra IP for port 80/443 mining, and use the correct port for https on the pool. As it stands there isn't much demand for any of the above so I'm loathe to messing with the status quo.
|
|
|
|
Looks like a block hit!!!
And there it is! It's nice to have confirmation everything's working perfectly fine on the pool, and to finally break through that 8 bit barrier for our 256th block! Congratulations to the miner, and all the people who contributed to help keep the pool alive. And only a 50TH miner! [2020-06-03 21:30:14.977] Possible block solve diff 26941303407284.085938 !
[2020-06-03 21:30:15.042] BLOCK ACCEPTED!
[2020-06-03 21:30:15.043] Solved and confirmed block 632928 by 1JfDwdSURAxgWqbQRQz4sY12wniGY3Sxtj.18
[2020-06-03 21:30:15.043] User 1JfDwdSURAxgWqbQRQz4sY12wniGY3Sxtj:{"hashrate1m": "49.1T", "hashrate5m": "52.9T", "hashrate1hr": "55.2T", "hashrate1d": "77.1T", "hashrate7d": "77.7T"}
[2020-06-03 21:30:15.043] Worker 1JfDwdSURAxgWqbQRQz4sY12wniGY3Sxtj.18:{"hashrate1m": "11.4T", "hashrate5m": "12.4T", "hashrate1hr": "12.7T", "hashrate1d": "13.6T", "hashrate7d": "13.5T"}
[2020-06-03 21:30:15.046] Block solved after 22464198046703 shares at 148.4% diff
|
|
|
|
|
Please note that from now on I will be archiving stats from users who have not mined in a month for efficiency reasons. If for some reason you want them reinstated, you can just ask.
|
|
|
|
The thing is that port 80 works just fine, HTTP requests go through just fine, when he managed to connect earlier I guess it was on can you enable port 80 for testing? stratum+tcp://solo.ckpool.org:80 if not, or if that doesn't work, setting up a relay in EU if other people agree to it will be worth it, I can only assume that a good number of miners reside in the east side of the world, so a relay pool will solve both ISP restrictions and latency. No, when he connected the denode port 80 hadn't been enabled yet. I can't enable port 80 on the pool since that's where the http server is. Connecting with http doesn't mean you'll be able to mine because there is probably a transparent proxy at his end which is proxying http traffic and would fail with stratum traffic. |
|
|
|
I believe CK said Iran is blocked from the pool. That could likely be your problem  No, I'm not blocking anything at all. |
|
|
|
Of course, I think this time is 15 seconds. Not 15 minutes!
I was just checking different ports on solo.ckpool.org.
I don't know how it got connected for a moment!
But now I checked again a few times. But it doesn't work anymore!
Yes 15 seconds sorry. How long are you waiting? Maybe you need to wait longer for it to connect? The ports that work on solo.ckpool.org are 3333, 443, and 4334 |
|
|
|
Try each of the following: denode.ckpool.org:3333
denode.ckpool.org:443
denode.ckpool.org:80
All is dead!  I saw you authorise on the pool at this time: [2020-05-28 23:15:29.387] Authorised client 1085395 worker 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR as user 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR and then drop at this time: [2020-05-28 23:15:44.775] Dropped client 1085395 user 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR worker 39hL2zBfBZAjJKLkPvrR85crgbsKqW8sCR So at some stage you successfully connected for 15 minutes (approximately 90 minutes ago). What did you do then? |
|
|
|
Try each of the following: denode.ckpool.org:3333
denode.ckpool.org:443
denode.ckpool.org:80
Update: Note I've disabled these since this post if anyone was trying them. |
|
|
|
|
If there's demand I could set up a relay in Germany with some of the funds given to me if that helps. However I'd have to point out that it is still better to mine directly to the pool.
|
|
|
|
I don't know what is the guilt of us who were born in Iran? Others rule. But we, the ordinary people of Iran, are deprived of the world.  I do not restrict access to the pool at all. It is out of my control. No political discussion here please. |
|
|
|
Hi
I check ping from the pool address. This is no problems and has no timeout.
But when I config and set pool addresses in ASIC Miner. The pool is dead.
Please help me what should I do?
I'm sorry for english, I'm using Google Translator.
Is your username a bitcoin address? Yes, the username is Bitcoin address. I also tested the BC1xxxx.... address, as well tested the 3xxxx.... and the 1xxxx.... address for username. with . dot worker name, and without worker name. stratum+tcp://solo.ckpool.org With all the port's. I even checked the addresses of solo4.ckpool.org and solo6.ckpool.org for the pool. In all cases, the pool is dead. I am from Iran. Could it be because of sanctions? However, I have no problem with other pools and the device works well. Iran blocks connections to the server. There is nothing you can do about it. |
|
|
|
Hi
I check ping from the pool address. This is no problems and has no timeout.
But when I config and set pool addresses in ASIC Miner. The pool is dead.
Please help me what should I do?
I'm sorry for english, I'm using Google Translator.
Is your username a bitcoin address? |
|
|
|
Will the pools proxy support work for 2PH worth of USB miners?
Yes Thank you. Did you mean the "tube/prisma" proxy? That wasn't designed for USB sticks in mind. I thought you meant running a local proxy yourself which would make far more sense. |
|
|
|
Will the pools proxy support work for 2PH worth of USB miners?
Yes |
|
|
|
Diff has now dropped if you guys want to crank up your rentals again |
|
|
|
|
Show Posts
