Topic: ckpool.org CLOSED (Read 162541 times)
Since decentralization is what actually works best, I see a future with more miners running & mining on their own p2pool nodes.
Please note, if you are still mining here, I have moved your mining to the solo pool now. If you happen to find a block before you switch away, you will be rewarded beyond your wildest dreams. Otherwise I suggest if you still want to pool mine, please switch now.
A novice question; How do I rescue my profits from the pool?. Because I see how from 0.00023000 they have dropped to 0.00013000, doing nothing.
Or should I give up the more than 4 months that I was mining in ckpool.
Thanks for being there.
Or should I give up the more than 4 months that I was mining in ckpool.
Thanks for being there.
you have learned an inexpensive lesson of small pool mining risk.
the pool takes too long to hit a block and folds.
all funds due are due on next block.
pool folded no new blocks.
I was due 0.026 btc when pool folded.
I effort to support small pools.
i support solo.ckpool
i support mmpool.org
this pool had my support it folded.
jonny bravo pool had my support it folded.
i have supported kano.is
i have supported bitminter
i can’t fully support these pools as my pockets are not than deep.
i only have 1.4 ph which allows me to toss some coins at smaller pools. but not the full support they need.
my thoughts are a pool needs to hit 15 blocks a month to survive.
most of these pools don’t do it. they dont have 300 or 400ph of hash.
Pool is now closed. I'm leaving the basic statistics up there for people to check on but the web interface is retired as well. Thanks everyone for your support till now and I'm sorry we couldn't make it work.
This pools payoutsystem is one of the best, a shame that not more people joined this pool.
Thank you for running it with no fee for a long time.
A novice question; How do I rescue my profits from the pool?. Because I see how from 0.00023000 they have dropped to 0.00013000, doing nothing.
Or should I give up the more than 4 months that I was mining in ckpool.
Thanks for being there.
Or should I give up the more than 4 months that I was mining in ckpool.
Thanks for being there.
The pool does not have a pool wallet, you get paied every time the pool found a block AND you are in the first 100
range of payouts (look the first posting).
So the answer is: give it up.
A novice question; How do I rescue my profits from the pool?. Because I see how from 0.00023000 they have dropped to 0.00013000, doing nothing.
Or should I give up the more than 4 months that I was mining in ckpool.
Thanks for being there.
Or should I give up the more than 4 months that I was mining in ckpool.
Thanks for being there.
I loved this pool the most, people would have earned the most if they moved their miners here, but alas.
Thanks for all these years and effort, the last zero fee pool with transparency will be missed...
Thanks for all these years and effort, the last zero fee pool with transparency will be missed...
Ck... thanks. and thanks for a great pool that ended much too soon.........
Hi,
Didn't this pool just get a block---- 630012?
{
"height": 630012,
"reward": 7.13663977,
"fee": 0.0,
"payouts": {
Didn't this pool just get a block---- 630012?
{
"height": 630012,
"reward": 7.13663977,
"fee": 0.0,
"payouts": {
No, that's not a block, that was the last work detail when the pool shut.
That block was found by poolin
https://btc.com/0000000000000000000eebcdd86b00ef4248a138c5face50a99afa0251d6aa5c
Hi,
Didn't this pool just get a block---- 630012?
{
"height": 630012,
"reward": 7.13663977,
"fee": 0.0,
"payouts": {
Didn't this pool just get a block---- 630012?
{
"height": 630012,
"reward": 7.13663977,
"fee": 0.0,
"payouts": {
Pool is now closed. I'm leaving the basic statistics up there for people to check on but the web interface is retired as well. Thanks everyone for your support till now and I'm sorry we couldn't make it work.
I'm not sure we can sway -ck to keep these pools open or not but I'd think of donating in support of keeping one or both open and available to the community. Likely a reasonable show of support to help -ck fund the pools and cover these recent losses will reduce the burden he shoulders for what looks like the 6000 users that enjoy his work.
Just a thought.
Just a thought.
CK, sad to hear.
Started here and learned a lot from everyone
Will end here also most likely
Wish you would reconsider but fully understand
Cheers from Canada
Dave
Started here and learned a lot from everyone
Will end here also most likely
Wish you would reconsider but fully understand
Cheers from Canada
Dave
Agreed - Thank you for your support of the mining community CK, and for working to make it right with the impacted miner.
Sad to read this.
Please note the following quote from the solo pool thread for more information, as it affects this pool as well as they share resources.
The practical upshot of this is that unfortunately it also means I will be closing ckpool.org as well after the halving. It pains me to do this knowing many of you have accumulated may blocks' worth of shares on this pool in anticipation of being rewarded on any follow-up block solves, but fortunately our last solve at 6% luck means the miners with the most accumulated shares had all gotten some reward for their hard earned shares to make up for earlier bad luck. As this pool works off rewards coming directly from the block solve to the miners, there is no pool wallet with any accumulated funds that are owed to anyone.
I apologise in advance, especially after saying that I would keep this pool up and running for as long as the community desired it, but I think the imminent death of the pool has been obvious for a long time now with its appallingly small hashrate and at some point someone needs to declare it as a lost cause. It should also come as no surprise to anyone given my minimal input on the forum for the last few years that my heart has really not been in it either.
My conclusion isn't a pretty one unfortunately and is mostly my fault to do with the resource capabilities of the pool hardware.
There was a single hash good enough for a block solve by rasmukri at 2020-05-10T12:34:16.287799Z but due to an unfortunate storm of coincidences a backup job was running on the pool at the time which overloaded the server pushing it heavily into swap memory. This caused the bitcoin daemon to be effectively out of sync with the blockchain for a while. Unfortunately this means that even though it was a potential block, it was not up to date with the current blockchain tip and was effectively stale anyway. The pool didn't record it as stale because it was a valid hash in the pool's eyes and its resource usage is much less than the bitcoin daemon so it was still operating normally, though complaining about not getting new block templates. Note that there was only one blocksolve hash good enough, and no other miners submitted potential block solves in that time. As is often the case with bitmain hardware, I would not trust it if it said it had solved blocks normally, but in this scenario one of them was very real.
As this pool doesn't make an awful lot of money, I could not really afford to dedicate much in the way of hardware resources to the pool. Since this is my fault for not ensuring the pool had enough resources for the bitcoin daemon, pool, and backup at the same time, I would like to come to an agreement with rasmukri by reimbursing him for his mining costs for time spent mining solo here, and as some degree of recompense I am willing to pay back double the cost of the mining. It may not be a full block's reward, but it is better than you could have earned mining in a regular pool. The only saving grace is that this didn't happen to any of the bigger miners who spent a lot dumping hashrate here in that time.
As of the time of posting this, the summary of your stats are as follows:
The 15 billion shares you submitted should give an approximation of how long you have mined here with your average 70TH (according to the weekly average.)
Please tell me if you find this satisfactory and we can take it to private message to resolve further.
In addition it is with a heavy heart that I find myself unable to cope with the potential stress of similar situations and loss of interest in maintaining any pool in this climate, along with the upcoming halving making it virtually completely impossible for individual miners to meaningfully mine and that I wish to close this and the shared pool after the halving.
Any existing miners you may wish to withdraw your hashrate sooner rather than later to prevent a similar situation happening between now and its closure, or you may wish to just hammer it hard until it's closed but I give no guarantees that it may not happen again and I will not be trying to reimburse anyone again.
There was a single hash good enough for a block solve by rasmukri at 2020-05-10T12:34:16.287799Z but due to an unfortunate storm of coincidences a backup job was running on the pool at the time which overloaded the server pushing it heavily into swap memory. This caused the bitcoin daemon to be effectively out of sync with the blockchain for a while. Unfortunately this means that even though it was a potential block, it was not up to date with the current blockchain tip and was effectively stale anyway. The pool didn't record it as stale because it was a valid hash in the pool's eyes and its resource usage is much less than the bitcoin daemon so it was still operating normally, though complaining about not getting new block templates. Note that there was only one blocksolve hash good enough, and no other miners submitted potential block solves in that time. As is often the case with bitmain hardware, I would not trust it if it said it had solved blocks normally, but in this scenario one of them was very real.
As this pool doesn't make an awful lot of money, I could not really afford to dedicate much in the way of hardware resources to the pool. Since this is my fault for not ensuring the pool had enough resources for the bitcoin daemon, pool, and backup at the same time, I would like to come to an agreement with rasmukri by reimbursing him for his mining costs for time spent mining solo here, and as some degree of recompense I am willing to pay back double the cost of the mining. It may not be a full block's reward, but it is better than you could have earned mining in a regular pool. The only saving grace is that this didn't happen to any of the bigger miners who spent a lot dumping hashrate here in that time.
As of the time of posting this, the summary of your stats are as follows:
Code:
"hashrate1m": "43.5T",
"hashrate5m": "68T",
"hashrate1hr": "112T",
"hashrate1d": "123T",
"hashrate7d": "70.7T",
"lastshare": 1589151959,
"workers": 3,
"shares": 15429406451,
"bestshare": 40661720994071.75,
"bestever": 40661720994071,
"hashrate5m": "68T",
"hashrate1hr": "112T",
"hashrate1d": "123T",
"hashrate7d": "70.7T",
"lastshare": 1589151959,
"workers": 3,
"shares": 15429406451,
"bestshare": 40661720994071.75,
"bestever": 40661720994071,
The 15 billion shares you submitted should give an approximation of how long you have mined here with your average 70TH (according to the weekly average.)
Please tell me if you find this satisfactory and we can take it to private message to resolve further.
In addition it is with a heavy heart that I find myself unable to cope with the potential stress of similar situations and loss of interest in maintaining any pool in this climate, along with the upcoming halving making it virtually completely impossible for individual miners to meaningfully mine and that I wish to close this and the shared pool after the halving.
Any existing miners you may wish to withdraw your hashrate sooner rather than later to prevent a similar situation happening between now and its closure, or you may wish to just hammer it hard until it's closed but I give no guarantees that it may not happen again and I will not be trying to reimburse anyone again.
The practical upshot of this is that unfortunately it also means I will be closing ckpool.org as well after the halving. It pains me to do this knowing many of you have accumulated may blocks' worth of shares on this pool in anticipation of being rewarded on any follow-up block solves, but fortunately our last solve at 6% luck means the miners with the most accumulated shares had all gotten some reward for their hard earned shares to make up for earlier bad luck. As this pool works off rewards coming directly from the block solve to the miners, there is no pool wallet with any accumulated funds that are owed to anyone.
I apologise in advance, especially after saying that I would keep this pool up and running for as long as the community desired it, but I think the imminent death of the pool has been obvious for a long time now with its appallingly small hashrate and at some point someone needs to declare it as a lost cause. It should also come as no surprise to anyone given my minimal input on the forum for the last few years that my heart has really not been in it either.
Pool is back up.
Please note I'm taking the pool down to investigate a block solve issue at the solo pool which may affect this pool too. I do not know how long the downtime will be and I'm terribly sorry about any inconvenience.
When I changed to 443 it did work on pool.ckpool.org:443 on the hiveOS software.
Are you in a part of the world where your government may have objections to bitcoin mining and is blocking port 3333? 443 is offered as an alternative because it's normally used for plain https traffic and not mining.
When I changed to 443 it did work on pool.ckpool.org:443 on the hiveOS software.
try
pool.ckpool.org:443
pool.ckpool.org:4334
or
depool.ckpool.org:3333
depool.ckpool.org:443
How do I connect the new generation miners on CKpool? I put some miners on HiveOS and then used below details but the pool shows dead on the miner. I know I am the one doing something wrong because other old gen machines are running fine on CK pool.
pool.ckpool.org:3333
BTC address
password: x
pool.ckpool.org:3333
BTC address
password: x
try
pool.ckpool.org:443
pool.ckpool.org:4334
or
depool.ckpool.org:3333
depool.ckpool.org:443
Jump to: