In addition, I've made publicly available the code as used by this solo pool now as well: https://bitbucket.org/ckolivas/ckpool-soloBear in mind it expects certain customisations and I will take no responsibility if someone misuses this in the community and creates a new solo pool with it, but perhaps someone skilled enough can fill the gap with it from me closing this pool. What about we make it a community pool? It would be a real shame to lose both the solo and main pools there a staple on bitcointalk for a lot of members and with the halving around the corner and price uncertainty things could change really quickly in the mining game and it would be a shame not to have this resource here if that we're to happen. i'm sure a few of us regulars might pitch in to ensure it's continuation. Who would you trust to administrate it, and how is that any different to the current solo pool? In addition it expects certain customisations and I'm not really keen to hand hold someone into how it works. |
|
|
|
In addition, I've made publicly available the code as used by this solo pool now as well: https://bitbucket.org/ckolivas/ckpool-soloBear in mind it expects certain customisations and I will take no responsibility if someone misuses this in the community and creates a new solo pool with it, but perhaps someone skilled enough can fill the gap with it from me closing this pool. |
|
|
|
Thanks for looking into that, you have no idea how excited I was when I saw the 40 trillion, until I opened my wallet. But at the time of you pulling my stats I guess it was right after my reboot of everything. It's strange how the stats work. I've been on here for almost a week and I've been pretty steady at (125th/s +-) but I guess it's gotta work up an average or something. I appreciate the offer to compensate and will take you up on it. I will also keep my miner pointed here untill you take it down, I have lottery winning dreams 😂😎 hashrate1m": "140T",
"hashrate5m": "124T",
"hashrate1hr": "115T",
"hashrate1d": "123T",
"hashrate7d": "70.8T",
"lastshare": 1589154060,
"workers": 6,
"shares": 15486797073,
"bestshare": 40661720994071.75,
"bestever": 40661720994071,
"worker":: Sure thing. The 70TH estimate is irrelevant, as the total shares already told me how much hash you've committed total. I can either work that out or you can just tell me how long it's been and at what electricity rate as I'm happy to do it on trust as I feel bad enough as it is. |
|
|
|
Please note the following quote from the solo pool thread for more information, as it affects this pool as well as they share resources. 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: "hashrate1m": "43.5T",
"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. |
|
|
|
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: "hashrate1m": "43.5T",
"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. |
|
|
|
|
So far I know the block got submitted but got rejected for being stale but the nearest block wasn't as close as I would have expected. The block that succeeded it was block 629777 by poolin.
|
|
|
|
|
Pool is back up, I've saved all the logs to investigate and will report back.
|
|
|
|
|
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.
|
|
|
|
"hashrate1m": "13.5T",
"hashrate5m": "13.1T",
"hashrate1hr": "13.4T",
"hashrate1d": "12.5T",
"hashrate7d": "8.77T",
"lastshare": 1589133889,
"shares": 2097197030,
"bestshare": 40661720994071.75,
"bestever": 40661720994071 I thought if a share was over the difficulty then it was a block? Or am I completely mistaken? Because 40 trillion is defiantly more than 16 trillion.  My miner says it found 2 blocks  This looks correct yet there was no successful block solve so I'm going to take the pool down to investigate. Sorry to all the people who want to mine in the lead-up to the halving. I don't know how long the pool will be down for. I'm terribly sorry about any inconvenience. |
|
|
|
Tell me if I'm right or wrong
We play with nonce (2^32) and use it to hash the block and hope the hash will be < target
So it means that for an antminer S9i (14TH/S), it takes 0.00028 seconds (2^32/14TH)
After this we increase an extra nonce from 0 to X. With an Antminer s9, we will reach (extranonce = 14TH/2^32) = 3500 in one second.
After this, there is the roll time, we update the ntime to the current time and put it extranonce to 0 and play again.
So I never try some extranonce more than 3500. But anyway, a extranonce < 3500 has the same luck than an extranonce > 3500, am I right ?
Also, in the coin base transaction, there is my BTC address, so it means that the block I tried to solve is unique ?
So it means, I can be lucky and solve the block with nonce to 0, extranonce to 0 and no change about ntime?
My conclusion about this is : It is really purely and simply luck to solve a block. Event with 1000PH or 1 bird neuron, you can win...
Arffff, I spent hours to modify my cgminer by creating some random behavior (changing extra nonce offset, modify the ntime in the future).
The fact is, more you have power, more you can have chance to win.
Yes, it doesn't matter whether you roll forwards, backwards, randomly, some pattern, or what. Every single hash has an equal chance of finding a block no matter what it's comprised of = 1 / 2^32 / current difficulty. All that matters, therefore, is how many unique hashes you throw at it. Cgminer already takes care that you never repeat hashes, and the pool takes care that different miners never repeat hashes. |
|
|
|
|
I'm going to be moving old user entries for clean up reasons as there are currently over 27,000 users there. Any from last year or before will be moved to solo.ckpool.org/users/old/ and still available manually but won't be accessible via the web interface.
|
|
|
|
Make sure your btc address is correct as well.
The one he posted was definitely a vaild bitcoin address. If he input it wrong into his miner, then solo would have just rejected him entirely. |
|
|
|
you can post the url that you were using?
I have seen people mine to the ckpool instead of the cksolo pool.
Hi JimJam, I'm just using the URL and port off the website: solo.ckpool.org:3333 Punched my BTC address in to the little search box and got a 404 Not Found result. copied and pasted it straight from the miners status page. Antminer S9 SE is the miner I'm using. It was reporting huge numbers of shares accepted so I'm guessing I had a good conneciton, but I was hoping to see it on the solo.ckpool site for confirmation.
There's no hashrate recorded to his username there either as far as I can see.
Thanks for checking in there -ck. Any ideas why that might be the case? Hopefully you don't have the default API permissions that bitmain fucked up their miners with that leads to them being hijacked and you were actually mining elsewhere? |
|
|
|
I had to give up on the solo pool. Not being able to find my miner meant I couldn't be confident the work I was doing was actually productive.
Reverted back to pool mining. Will tinker again with the solo pool once I have some time.
If anyone has any suggestions as to why I couldn't find my username to verify successful connection, it'd be greatly appreciated.
Best of luck to those hunting a block!
you can post the url that you were using? I have seen people mine to the ckpool instead of the cksolo pool. There's no hashrate recorded to his username there either as far as I can see. |
|
|
|
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. |
|
|
|
The pool shows as dead when I put in following details
solo.ckpool.org:3333
Bitcoin address
Password: x
I have tried 443 and 3333 both.
The software on the miner is HiveOS.
The reasons are usually one of the following: A temporary routing issue between you and the pool. Your username is not a valid bitcoin address. Some IP addresses have been blocked due to multiple previous failed attempts to connect. |
|
|
|
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
Apparently I hear that bitmain crapped out the S17(?) in terms of only supporting a tiny coinbase size and they won't work on this pool as a result. I haven't confirmed this myself but it would explain why some miners can connect to the solo pool but not this one. I also hear that there is a custom firmware out there that addresses this. |
|
|
|
can i mine with a BECH32 (P2WPKH) --> bc1q6lj97gc2mnntxuw2eu52t62x2g2zue42h20daa adress on this solo pool?
not that we find a block and not get paid?
i mined bevor only with BASE58 (P2PKH) adresses.
Best regards
Willi
Yes indeed. ckpools were the first pools to support bech32 mining. |
|
|
|
|
Show Posts
