Another situation is that when the computing power of the pool can no longer keep up with the future difficulty, it cannot efficiently and continuously produce the blocks with luck. From the mine pool manager to the miners, maybe someone knows what it is like problem or result  There's no such thing. It's just as much work dealing with diff 1 and cpu miners as it is diff 1 quadrillion and quantum computers. |
|
|
|
|
1 correct
2 nonce happens so quickly the entire range is always done by hardware. Extranonce is set by pool and also incremented by hardware, reset with every work update
3 all the churn handled by miner
None of this makes any difference to probability.
|
|
|
|
Congratulations to miner bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6 with ~1PH of hashrate at solving the 277th solo block at solo.ckpool.org [2023-08-18 23:35:26.985] Possible block solve diff 166457402539689.843750 !
[2023-08-18 23:35:27.053] BLOCK ACCEPTED!
[2023-08-18 23:35:27.056] Solved and confirmed block 803821 by bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6
[2023-08-18 23:35:27.056] User bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6:{"hashrate1m": "1.05P", "hashrate5m": "1.04P", "hashrate1hr": "1.01P", "hashrate1d": "1.01P", "hashrate7d": "1.01P", "shares": 1944392199944, "authorised": 1685417900}
[2023-08-18 23:35:27.056] Worker bc1q2za4ejga366sn288273pty8trasn5zs4y9hqg6:{"hashrate1m": "1.05P", "hashrate5m": "1.04P", "hashrate1hr": "1.01P", "hashrate1d": "1.01P", "hashrate7d": "1.01P"}
[2023-08-18 23:35:27.062] Block solved after 66873411563189 shares at 127.6% diff
A miner of this size would solve a block solo only once every 7 years at the current difficulty. |
|
|
|
Wondering if the more experienced ppl here can help, being a smallish miner I'm curious about how I would calculate my personal "luck" percentage as of now.
I've been consistently throwing a variety of different ASICs (totaling from 80T to a few PHs at a time) to this pool for over a year, and accross a few different wallets. Because it's not been consistnetly X TH/s I'm not sure how I can figure out approximately where I am. Am I still at 1% am I at 10% or more? Is it a function of total shares submitted relative to total network difficulty? And if so what is the formula to figure it out?
I've been tracking some data, like for example in total I've submitted approx this many shares:
1,948,660,040,000
And my best share thus far is:
1,474,956,179,560.041
What other info do I need to calculate my total personal luck at this point? And yes I know, it's just a simple game of odds and totally random, but after over a year I'd like to know a little more accurately just how lucky I've been.
Appreciate any info or help in figuring this out - thanks folks!
Sadly there is no such thing as "progress towards a block". Only your hashrate from this point onwards counts. Your probability is purely related to what your current hashrate is. |
|
|
|
|
Last small miner found a block last year. It's simply an odds game - of course the terahash miners will find blocks thousands of time more frequently than the gigahash miners, since they have 1000x more hashrate.
|
|
|
|
|
Only the solo ckpool branch code is maintained, and make sure to use the latest version from git, which is currently tagged as 0.9.9
|
|
|
|
Could someone suggest a verfified webhosting VPS where I could run ckpool as a ckproxy stratum proxy?
OVHCloud host the solo pool and offer VPSs. A ckproxy doesn't need much horsepower, storage, nor ram. https://us.ovhcloud.com/vps/ |
|
|
|
Except that no real mining hardware uses only 20-30W.
I'm only running one Compac F its about 17Watts at the socket and its being run by a Raspberry PI Zero 2W, which is about 3 watts at the socket so in total approx 20Watts. As a lottery miner thats great, it blends into the background a costs litterally nothing to run, especially given the house is running mostly on solar & battery. But, yes a real miner you're looking at more than 3000Watts at the socket! Yep that's fair. My concern is there's been a resurgence of trying to use equipment that does absurdly low hashrates lately (in the KH range). That's not lottery, it's sheer folly. |
|
|
|
|
Except that no real mining hardware uses only 20-30W.
|
|
|
|
Does anyone have a discord channel invite for ck pool
No one was using the discord channel so I shut it down. |
|
|
|
How will I know my miner has found something?
Money appears in your wallet. |
|
|
|
Congratulations to miner 3EHpvbs5ar7DWiux1AQ5JMB2zTBE6wzX7d with only 42TH for solving the 276th solo block at solo.ckpool.org! [2023-06-21 03:22:26.321] Possible block solve diff 148673543161298.468750 !
[2023-06-21 03:22:26.406] BLOCK ACCEPTED!
[2023-06-21 03:22:26.406] Solved and confirmed block 795268 by 3EHpvbs5ar7DWiux1AQ5JMB2zTBE6wzX7d.fat-antminer-00
[2023-06-21 03:22:26.406] User 3EHpvbs5ar7DWiux1AQ5JMB2zTBE6wzX7d:{"hashrate1m": "43.2T", "hashrate5m": "40.6T", "hashrate1hr": "41.8T", "hashrate1d": "41.2T", "hashrate7d": "41T", "shares": 116230614387, "authorised": 1685417899}
[2023-06-21 03:22:26.406] Worker 3EHpvbs5ar7DWiux1AQ5JMB2zTBE6wzX7d.fat-antminer-00:{"hashrate1m": "11.1T", "hashrate5m": "13.1T", "hashrate1hr": "13.8T", "hashrate1d": "13.6T", "hashrate7d": "13.6T"}
[2023-06-21 03:22:26.409] Block solved after 17167552901929 shares at 32.8% diff
A miner of this size would only solve a block on average every ~160 years. For the duration they've been mining, this was a 1 in ~450 chance. |
|
|
|
Woah that article got a lot of people pointing their rigs toward CK hashrate1m": "637P Those sorts of short term high hashrate rentals just after a block solve are common. They don't last long and we always go back to our baseline level which is around 20PH now. |
|
|
|
|
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. |
|
|
|
|
Show Posts
