Quick question CK. Why do rentals show shares like this with lots of zeros at the end I noticed most rentals I do have this but when I rent single miners or put some of my own on they show the shares as full numbers? Rental Example "hashrate1m": "0",
"hashrate5m": "0",
"hashrate1hr": "0",
"hashrate1d": "1.35T",
"hashrate7d": "42.4T",
"lastshare": 1643974944,
"shares": 14695000000,
"bestshare": 19554100453.00714,
"bestever": 19554100453
Non-rental "hashrate1m": "0",
"hashrate5m": "0",
"hashrate1hr": "108M",
"hashrate1d": "3.45T",
"hashrate7d": "1.75T",
"lastshare": 1644465743,
"shares": 312323777,
"bestshare": 650426091891.621,
"bestever": 650426091891
Because the share count is a multiple of the share difficulty, and rentals are using shares on a port with a minimum difficulty of 1 million, so they'll always be a multiple of 1 million. The other port doesn't have a lower limit. |
|
|
|
So has anyone tried running their asic on solo ck pool for a full year?
Quite a few people have been mining here for years on end. |
|
|
|
you are very pessimistic. I think people will stay. And for my part I would stay even 5 years if necessary, even if I do not solve any block. At least I would have participated in decentralized bitcoin mining. This reason alone is worth all the gold in the world.  Thanks, but I've been in this mining game for 11 years. I'm a realist, not a pessimist, but appreciate your sentiment greatly. |
|
|
|
The hashrate of the pool its now at 854.91ph/s  https://btc.com/stats/pool/Solo%20CKImagine for a moment that we could reverse the trend and that more and more miners would join us. And that the norm becomes solo mining. No it's not. The pool predicted hashrate from block explorers is based on average block solve frequency - if a pool has a period of luck, its hashrate appears higher. In this case solo's luck has been very good for the last 5 blocks so it grossly exaggerated there. The correct current pool hashrate is what you see on the pool itself, and is around 30PH, which is still a lot higher than it's been for the last few years as a result of the recent publicity. It's impossible to know if this hashrate will be maintained, but it's my guess the next unlucky block will have many miners leaving when they don't get any rewards, and the hashrate will slowly peter out back to its original ~5PH baseline. |
|
|
|
Hi guys,
What do you think, what is more efficient in solo, one 14TH asic or three asics with 4TH? Who is understand how it works?
"Efficient" is a word implying hashrate for power usage, but you are not listing power usage. If you are talking about your chance of finding a block, only the total hashrate matters. 14TH is more likely to find a block than 12TH. |
|
|
|
man - what does that make this year? 5 or 6?
5 in short succession, all very lucky blocks. It can't continue indefinitely. |
|
|
|
Congratulations to yet another small miner with 13TH! [2022-02-03 01:17:47.959] Possible block solve diff 49404145846653.273438 !
[2022-02-03 01:17:47.981] BLOCK ACCEPTED!
[2022-02-03 01:17:47.981] Solved and confirmed block 721575 by 1ADwc721c1KuqhHy2vuL8b96G6DEDAhSUX
[2022-02-03 01:17:47.981] User 1ADwc721c1KuqhHy2vuL8b96G6DEDAhSUX:{"hashrate1m": "13T", "hashrate5m": "14.4T", "hashrate1hr": "15.2T", "hashrate1d": "10.2T", "hashrate7d": "2.21T"}
[2022-02-03 01:17:47.982] Worker 1ADwc721c1KuqhHy2vuL8b96G6DEDAhSUX:{"hashrate1m": "13T", "hashrate5m": "14.4T", "hashrate1hr": "15.2T", "hashrate1d": "10.2T", "hashrate7d": "2.21T"}
[2022-02-03 01:17:48.019] Block solved after 1038303277333 shares at 3.9% diff
|
|
|
|
very pleased about my favorite in past times CK is back I never went anywhere, and neither did this pool. |
|
|
|
So how do you determine if the ISP provider is blocking the port? I've tried to use different port on ckpool and still come up as dead network? I've read through the thread and know that the network is very much Alive. Any thoughts or suggestions?
Try the proxy offered about a page back, it's located in .de and often helps people in the middle east connect for example, who are blocked from that particular datacentre (unfortunately). |
|
|
|
That is not at all the response I get when I check that site. Besides, the pool is running fine as I can see, but routing across the earth is often funky. See: https://www.internetweathermap.com/ |
|
|
|
|
I've shut down the asicminer prisma proxy port as there were very few remaining users, and some occasional unintentional abusers, and confused users. I can't imagine there are many still in operation out there but sorry about any inconvenience if you were trying to use them.
|
|
|
|
Hi. I've tried using both the . and then the _ and get same result. It still shows network as Dead for ckpool via port 3333. I've tried the other ports too per the CK Pool Instruction.
@HagssFIN
There are 2 common reasons for not being able to connect: 1. The most common one is that you have a typo in your bitcoin address, or added a space somewhere, like before the address. 2. You are in a part of the world where routing is blocked to the datacentre where the pool is hosted - this is unfortunately out of my control as I don't block anyone from mining there. |
|
|
|
Congratulations to bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet with approximately 1.14PH! [2022-02-01 08:27:35.681] Possible block solve diff 36770979250673.867188 !
[2022-02-01 08:27:35.728] BLOCK ACCEPTED!
[2022-02-01 08:27:35.730] Solved and confirmed block 721310 by bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet
[2022-02-01 08:27:35.731] User bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.731] Worker bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet:{"hashrate1m": "1.18P", "hashrate5m": "1.14P", "hashrate1hr": "1.12P", "hashrate1d": "1.15P", "hashrate7d": "1.12P"}
[2022-02-01 08:27:35.767] Block solved after 5496218477727 shares at 20.6% diff
|
|
|
|
Hey CK how do I get like a running feed of the pool? Like one that keeps running and showing if and when a block is found by pur Solo pool?
It's all done manually since they're so infrequent so this forum thread primarily or my twitter feed is the best place as they'll always be announced by me. |
|
|
|
Your hashrate is so ridiculously small it will take a week for the pool to even register that you're mining. yes 333mh/s is not high  its just 4 fun, but still would be nice to see stats ^^ Wait a week and you might see them. |
|
|
|
Your hashrate is so ridiculously small it will take a week for the pool to even register that you're mining. |
|
|
|
"hashrate1m": "116T",
"hashrate5m": "115T",
"hashrate1hr": "109T",
"hashrate1d": "89.9T",
"hashrate7d": "25.1T",
"lastshare": 1643270035,
"workers": 1,
"shares": 4030448508,
"bestshare": 4682952077.431146,
"bestever": 4682952077,
"worker": [
{
"workername": "3Dt3YF9tU6YsmApvpHUJDDcCevyPzrmrr4",
"hashrate1m": "116T",
"hashrate5m": "115T",
"hashrate1hr": "109T",
"hashrate1d": "89.9T",
"hashrate7d": "25.1T",
"lastshare": 1643270035,
"shares": 4030448508,
"bestshare": 4682952077.431146,
"bestever": 4682952077
hi everyone
does everything seem correct to you?
I mine on port 3333
should I change to solo.ckpool.org:4334
OR
solo.ckpool.org:3335
What do you think ?
i have s19 104TH
Thanks for ur answers
Leave it as is. 3333 is the right port for you. All seems working fine. |
|
|
|
On an antminer pw field, would that be mindiff=442 ?
Ckpool ignores anything in the password field. It only works with cgminer that supports the suggest-diff option directly. There's no need to adjust diff manually anyway, the pool will slowly choose what's best for you. |
|
|
|
|
Show Posts
