|
114 ms is perfectly fine. Ideally I'd like to have an eu based server as well, but the pool is just too small to justify it.
|
|
|
|
Different ports handle pool difficulty differently, there is no way your miner would work better/worse just because of that, using high difficulty means fewer shares reported to the pool but every share is worth more, reported hashrate will fluctuate when you use high diff on a slow gear, eventually it will catch up and average out, but it would be pretty normal to see a 100th gear reports 500th and then 5th, but that doesn't change the fact that it's nothing but a 100th gear.
You and the pool want something in between, something reasonable, not too low that submits every share every ms and puts stress on the server, your router, and everything involved, also not something too large, where your miner needs 30 mins to find a share above the set difficulty and gives you all those wired readings and then you don't know what's the real hashrate your miner is getting.
Note that, all of that has exactly no effect on your chances of hitting a block, any share that hits a block with be greater than the difficulty set by any port/pool, but to ensure a smooth operation, always just the ports specified by the pool operator, if it tells you port x is for rental, it really means it's for rental, using it to mine directly could create issues along the way.
This is an absolutely correct response and perfect advice. The only thing I can add is the two ports are on the same pool instance entirely, so apart from the starting diff, they are handled identically internally by the pool. |
|
|
|
One doubt, I am currently mining in CKpool with 6 S19J PRO,
Do I use the 3333 or the 4334?
Everyone except for rentals should use 3333. |
|
|
|
Pool restart due for a couple of hours. My fee payout address will change but otherwise no change will be visible to users. As always, I expect downtime to be negligible and virtually imperceptible to miners.
The pool has been restarted. The solo fee address is now bc1q28kkr5hk4gnqe3evma6runjrd2pvqyp8fpwfzu . The only other change made is that stratum updates are now sent every 30 seconds, which updates transactions more often. There should be no visible change to users. Mine on! |
|
|
|
|
Pool restart due for a couple of hours. My fee payout address will change but otherwise no change will be visible to users. As always, I expect downtime to be negligible and virtually imperceptible to miners.
|
|
|
|
Sometimes it is very interesting that after people are hit, the computing power will disappear.
That does more apply to pools, when people realize what amount of btc they get for the hashrate they provide to the pool, and the electrical cost they had to cover for doing that. On the solopool they are aware of it and mine for themself, so it is unlikley that they disapear after they found a block. True. if anything, hashrate usually goes up here after a block when people get tempted by the probability of solving a block solo. It then tends to calm down over the next month or so. |
|
|
|
Is there any way to find out what region of the world is housing this very lucky S9? Wondering what type of magical Internet connectivity they have
I wouldn't reveal that information unless the miner wished it, and magical internet connectivity has nothing to do with it. |
|
|
|
Congratulations to miner 151XTfHBfaDqoNWGGeYobNX2YzFFWuB5YD with only 17TH for solving the 275th block at solo.ckpool.org! [2023-06-09 18:58:54.377] Possible block solve diff 463250108543599.500000 !
[2023-06-09 18:58:54.458] BLOCK ACCEPTED!
[2023-06-09 18:58:54.460] Solved and confirmed block 793607 by 151XTfHBfaDqoNWGGeYobNX2YzFFWuB5YD.ASIC2
[2023-06-09 18:58:54.460] User 151XTfHBfaDqoNWGGeYobNX2YzFFWuB5YD:{"hashrate1m": "18.5T", "hashrate5m": "16.8T", "hashrate1hr": "15.6T", "hashrate1d": "15.6T", "hashrate7d": "15.7T", "shares": 9230494791, "authorised": 1685417900}
[2023-06-09 18:58:54.460] Worker 151XTfHBfaDqoNWGGeYobNX2YzFFWuB5YD.ASIC2:{"hashrate1m": "18.5T", "hashrate5m": "16.8T", "hashrate1hr": "15.6T", "hashrate1d": "15.6T", "hashrate7d": "8.55T"}
[2023-06-09 18:58:54.462] Block solved after 15306888081924 shares at 29.9% diff
As you can see they solved the block after only 9230494791 shares making this an absurdly lucky block solve (if they have been using the same username at all times). A miner of this size would only solve a block about once every 450 years on average. This is the first mainnet block solved with the updated pool code as far as I'm aware and whilst it was heavily tested on testnet, it is always a relief to see real blocks solved as well. I will be restarting the pool again in the near future for some minor updates once more (local cosmetic reasons for myself). Mine on! |
|
|
|
Pissweak hashrates take forever to show up because the pool can't even tell if you're hashing often for days or even weeks.
That is a ridiculous hashrate for the modern world. |
|
|
|
|
Pissweak hashrates take forever to show up because the pool can't even tell if you're hashing often for days or even weeks.
|
|
|
|
How many times per second/minute a miner retrieves a new block template with the newest list of transactions from ckpool?
Not ckpool distributes the block template actively, instead the miner has to call it from bitcoin daemon with get_transactions or get_txnhashes – so at the end the interval depends of the mining firmware, right?!
Referring to this, are there big differences when I use a Newpac with CGminer or a S9 with Braiins or Bitmain as mining-software?
No, I set the interval and they are pushed out to miners regularly at 60 seconds here. You can't control this at the client end. |
|
|
|
Hi. How is everyone? So I was hoping someone could explain what authorised means on the wallet monitoring page for this pool. I use de.ckpool.org for I am closer to europe. I have used this pool for years. And now for some reason between the bestever hash and where it says worker. It says "authorised: 1685417900," I have used ck pool for about 5 years and this has never shown up before and was hoping someome on here could help with that. I listed below the page. Thank you.
hashrate1m": "8.44T",
"hashrate5m": "8.14T",
"hashrate1hr": "5.75T",
"hashrate1d": "4.17T",
"hashrate7d": "2.8T",
"lastshare": 1685493742,
"workers": 3,
"shares": 1308792817,
"bestshare": 6969965998.88351,
"bestever": 6969965998,
"authorised": 1685417900,
"worker": [
Hi. Firstly there isn't really a de.ckpool.org as I shut down the extra server for it wasn't worth the hassle and cost, it just points to solo.ckpool.org so unfortunately there's no benefit to using it. I just left it there for historical compatibility. Second, I explained authorised 2 posts ago. It's a unix timestamp for when a user first authorises on the pool. I plan to use it for when users solve blocks to know how long they've been mining for. It won't be accurate for anyone mining before the last restart of the pool since that's the time they'll get on that field, but will help for those transient miners and in the long term. |
|
|
|
The pool has now restarted, having been updated to version 0.9.7 of the ckpool solo code, and the bitcoin daemon has been updated to the (ck modified) version 25.0.
Mine on!
Great ! I didn't find what means the new line "authorised" ? That's to know when a user first authorised on the pool. It won't be much good for those who were already on before this restart, but it will let me know how long someone has been mining for when they solve a block. |
|
|
|
|
The pool has now restarted, having been updated to version 0.9.7 of the ckpool solo code, and the bitcoin daemon has been updated to the (ck modified) version 25.0.
Mine on!
|
|
|
|
We are started Blockparty 39 with 20PHs
Live View Link:
you noticing the hast rate is all over the place? Dropping down below 1th for a bit then up and back down? This is likely to be because someone temporarily pays a higher price for hashrate, directing it away from the group's rental at a price premium. It doesn't make sense to pay such a premium so the group is doing the correct thing by purchasing hashrate at the lowest possible price. They will still get their total hashes overall, just over a longer period. |
|
|
|
Version 0.9.7 of the solo ckpool code has been tagged, and there is now a README-SOLOMINING to help people set up their own backup local solo mining. Get it here: https://bitbucket.org/ckolivas/ckpool-solo/src/v0.9.7/This code will be deployed on the pool in the next couple of days. |
|
|
|
|
Hi all.
I've been slowly updating and testing the solo ckpool code to make it more useful for general use, updating it to work best with the latest version of bitcoin core, added some minor improvements and fixed a few minor bugs along the way. It's been undergoing intensive testing the last week and is in its final regression tests now, solving blocks on testnet. In the next week sometime I'll be planning to update the code used on this pool after testing is complete, along with an updated version of bitcoin core. There will be no changes to the end users and downtime should be almost undetectable. I will give advance warning of when this will be happening so people can plan not to dump hashrates here over that period if that concerns them. As with any update there are always risks of instability but I will only be updating once testing has confirmed it is working to my satisfaction.
|
|
|
|
Some people rotate their mining addresses so you may never get to know exactly how long they've been mining.
Do they change management for any reason? I had not taken this into account. Sometimes it's for privacy reasons, sometimes they do it for luck reasons since miners tend to be superstitious, and sometimes it's just for practical wallet management reasons. |
|
|
|
Some of you may not be aware, but I've been contacted by Futurebit to assist them in getting solo mining built into their standalone miner/node hardware. I've been updating the solo ckpool code to make it more generalisable and work properly with the latest stable version of bitcoin core and on the testnet and regtest networks. Going forward, the solobtc code is the only ckpool code I'm planning on updating and maintaining. This is not going to replace this solo pool, as the dedicated hardware in a high speed low latency data centre is still a better choice for minimising the risk of orphan blocks, but the idea is that anyone should be able to mine solo locally as either their final fallback, or by choice. This could act as an important safeguard to preserve bitcoin mining in future should there be coordinated attacks on the major pools out there. The code is freely available and not confined to use by Futurebit alone. Even if other manufacturers decide to take the GPL code and illegally fork their own version of it without providing source code as they have done with cgminer, it will still be a net positive.
Although I don’t know much about it, it should be able to help many people in the future. When I looked at the cgminer version introduced by my predecessors, it seemed that there was no development and available binary executable files. It was only in 2018. I just don’t understand the reason for stopping the development. I believe these powerful ones people will work it out  There was nothing to develop, all the mining hardware they were doing their own versions of cgminer and drivers in house. There remained no reason to maintain a general version that worked on all hardware - nor was there any way to write drivers for their hardware with their closed systems. |
|
|
|
|
Some of you may not be aware, but I've been contacted by Futurebit to assist them in getting solo mining built into their standalone miner/node hardware. I've been updating the solo ckpool code to make it more generalisable and work properly with the latest stable version of bitcoin core and on the testnet and regtest networks. Going forward, the solobtc code is the only ckpool code I'm planning on updating and maintaining. This is not going to replace this solo pool, as the dedicated hardware in a high speed low latency data centre is still a better choice for minimising the risk of orphan blocks, but the idea is that anyone should be able to mine solo locally as either their final fallback, or by choice. This could act as an important safeguard to preserve bitcoin mining in future should there be coordinated attacks on the major pools out there. The code is freely available and not confined to use by Futurebit alone. Even if other manufacturers decide to take the GPL code and illegally fork their own version of it without providing source code as they have done with cgminer, it will still be a net positive.
|
|
|
|
|
Show Posts
