|
I apologise for being narky though. This is the 12th year I've been providing bitcoin mining software and services, and wanted to get out of the mining scene completely, but the solo mining community literally funded me staying here because they value my service. I do not believe my integrity would be up for questioning, nor that anyone would believe I was doing something nefarious, especially since my persona has been public and people know exactly who I am and where I'm located.
|
|
|
|
|
It was the biggest load of horse shit accusation ever and I just treated it as a troll. It was certainly not posted in good faith. There is no fucking way I'd ever mine any shitcoin let alone in secret without the users knowledge. Merge mining fucking shitcoins shows up in the blocks you create anyway so the evidence would be glaringly obvious. Now go and accuse others of moronic behaviour and leave us alone.
|
|
|
|
wow, what for a small miner, so a next block solved with a very small hashrate @ck, can you post your normal stats... too? Not at the moment unfortunately, as I'm away on vacation and don't have a secure way to log into the server. |
|
|
|
On the bitcoin wiki, I've just read that we could mine testnet blocks on solo ckpool If you find a block, 99% of the 6.25 BTC + transaction fees get generated directly at your bitcoin address.
1% goes to the operator to operate the pool and contribute to further ckpool code development.
For testnet:
If you find a block, 100% of the testnet coins + transaction fees get generated directly at your bitcoin address.
Link : https://en.bitcoin.it/wiki/Solo.ckpoolWas it possible previously or is it a mistake ? I was not aware that testnet blocks were solvable via ckpool I did run a testnet pool for a while, but that hasn't been for years. |
|
|
|
Hello guys! There is block 767395 hit by mmpool today, and in its coinbase tags you can see "ckpool" abbreviation. How does it work? Thanks
That just means they're using the ckpool software I wrote which is all free software anyone's allowed to use. |
|
|
|
Hello guys! Since last block was hit here in september, what is possibility that someone on ckpool will hit it again? I mean in percents, what is "pool luck" at the moment? thanks
Luck doesn't change over time. Only the current hashrate determines the chance and at its current hashrate the chance of finding a block remains very low per day. |
|
|
|
|
Looking through the logs I can see one miner submitting mostly rejects - all below target level, suggesting dodgy firmware on his hardware, but I don't see anything else untoward. That might be enough on its own. I suggest each individual user check their own stats and see if their hashrate at the pool reflects their hardware - ckpool reports hashrate based ONLY on accepted shares.
|
|
|
|
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.
"accepted": 24575964250308, "rejected": 8543041616789,
Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.
Just curious...
It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid. So there's enough shitty firmware out there running in miners solo mining on this pool to cause over 1/3 of the total shares submitted by the entire solo pool to be rejected? That seems crazy! I could understand if a small portion of the miners connected to the pool had that issue but over 1/3 of our shares submitted are being rejected. Is this due to rentals maybe? I'm not an expert by any stretch in this area which is why I'm trying to understand more about it. It just seems like a very gross inefficiency if 1/3 of our total shares on the solo pool as a whole are being rejected. It's probably one miner, likely a rental related phenomenon. I might investigate. |
|
|
|
Question for you all. I was looking at the solo pool stats and noticed the number of rejected shares versus total shares accepted.
"accepted": 24575964250308, "rejected": 8543041616789,
Is it normal to have such a high ratio of rejected to accepted shares? It's almost 35%.
Just curious...
It's not normal, it's likely shitty asic firmware. If the reported hashrate is still fine and consistent with the hardware then just ignore it, it means it's submitting shares below difficulty or something stupid. |
|
|
|
I would add that CKPool has been almost two months with an average of 19P more or less without hitting a block, could it be due to the increase of the difficulty in these last months?
I think that 19P is like 190 asics of 100Th/s and it scares me to believe that it takes so many machines to not hit a block in 2 months.
Nope, it's just because 19P is a piddly small amount of hashrate. The difficulty increases have only been modest recently. |
|
|
|
Hi!
Where get contacts support of this pool?
In IRC not answer.
You are in the support thread. Ask your question. |
|
|
|
I ping, your server change name to solo4.ckpool.org, 395 ms.
Too slow?
jack1@hp:~$ ping solo.ckpool.org -c 5
PING solo.ckpool.org (51.81.56.15) 56(84) bytes of data.
64 bytes from solo4.ckpool.org (51.81.56.15): icmp_seq=1 ttl=38 time=512 ms
64 bytes from solo4.ckpool.org (51.81.56.15): icmp_seq=2 ttl=38 time=433 ms
64 bytes from solo4.ckpool.org (51.81.56.15): icmp_seq=3 ttl=38 time=355 ms
64 bytes from solo4.ckpool.org (51.81.56.15): icmp_seq=4 ttl=38 time=379 ms
64 bytes from solo4.ckpool.org (51.81.56.15): icmp_seq=5 ttl=38 time=300 ms
--- solo.ckpool.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 299.737/395.647/511.561/72.009 ms
Yes definitely too slow. Try solo6.ckpool.org if your network supports IPV6. |
|
|
|
Haciendo ping a solo.ckpool.org [51.81.56.15] con 32 bytes de datos:
Respuesta desde 51.81.56.15: bytes=32 tiempo=116ms TTL=51
Respuesta desde 51.81.56.15: bytes=32 tiempo=116ms TTL=51
Respuesta desde 51.81.56.15: bytes=32 tiempo=115ms TTL=51
Respuesta desde 51.81.56.15: bytes=32 tiempo=115ms TTL=51
I have this data, which range would be the best to follow in CKPool?
That's fine. Up to 150ms should still be fine. |
|
|
|
on CKPool : PING solo.ckpool.org (51.81.56.15): 56 data bytes
64 bytes from 51.81.56.15: seq=0 ttl=51 time=265.554 ms
64 bytes from 51.81.56.15: seq=1 ttl=51 time=265.200 ms
64 bytes from 51.81.56.15: seq=2 ttl=51 time=265.054 ms
64 bytes from 51.81.56.15: seq=3 ttl=51 time=265.302 ms
64 bytes from 51.81.56.15: seq=4 ttl=51 time=265.159 ms
64 bytes from 51.81.56.15: seq=5 ttl=51 time=265.413 ms
--- solo.ckpool.org ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 265.054/265.280/265.554 ms
hi,.. with ping that big, is it still worth it for me to mine on CKPool? I'd say that's an excessively high ping time and would advise against it unless you're dead set on mining solo instead of on a regular shared pool. |
|
|
|
[2022-09-06 09:51:49.853] Possible block solve diff 127942493531046.984375 !
[2022-09-06 09:51:49.919] BLOCK ACCEPTED!
[2022-09-06 09:51:49.924] Solved and confirmed block 752868 by 15Hgp1dLmdNfZCYVysikTsJXoEL3kMpPz3.58m21
[2022-09-06 09:51:49.924] User 15Hgp1dLmdNfZCYVysikTsJXoEL3kMpPz3:{"hashrate1m": "256T", "hashrate5m": "269T", "hashrate1hr": "281T", "hashrate1d": "189T", "hashrate7d": "57T"}
[2022-09-06 09:51:49.924] Worker 15Hgp1dLmdNfZCYVysikTsJXoEL3kMpPz3.58m21:{"hashrate1m": "58.1T", "hashrate5m": "57.6T", "hashrate1hr": "57.9T", "hashrate1d": "38T", "hashrate7d": "14.9T"}
[2022-09-06 09:51:49.964] Block solved after 69526501463599 shares at 224.4% diff |
|
|
|
HI all. My credit card was recently the subject of fraud so I had to cancel it and am awaiting reissue. Unfortunately the hosting provider also happened to try to autopay shortly after the card was cancelled. Please don't fire up any big rentals or throw a lot of hashrate at the pool until this is resolved in case the hosting provider suspends or cancels the service before I can rectify it.
Shouldn't you have several cards? In the UK, debit cards (access to normal funds in the bank, without credit line) are free with every bank account. And credit cards can be had too. It is normal to have several bank accounts opened, with a bunch of cards. That way, one is never left on mercy of one banking institution. I lost my phone with it, and the 2FA that went with it so I couldn't log in to even use my other credit card. |
|
|
|
Credit card issue resolved; you may fire when ready  |
|
|
|
|
HI all. My credit card was recently the subject of fraud so I had to cancel it and am awaiting reissue. Unfortunately the hosting provider also happened to try to autopay shortly after the card was cancelled. Please don't fire up any big rentals or throw a lot of hashrate at the pool until this is resolved in case the hosting provider suspends or cancels the service before I can rectify it.
|
|
|
|
Hi guys, Could you tell me what an acceptable ping time would be for the address http://solo.ckpool.org? Is 125ms ok? Does this time interfere with anything for the miner to find a block and send the pool to be accepted? Would it be possible to improve this time through another address for example? or what would be the best way to check the ping time for the pool? Thanks. That ping time's fine. The only way to improve ping time is to be physically closer to the server. Does this time influence anything to harm finding and processing a block in a timely manner? Do you have another point on the server or is it just the one in the link? Thanks. It means the block takes half that time to get to the server if you solve one. There is an absolutely minuscule increase in the risk of a block being orphaned in that time. However the pool hardware confirms it's a block very quickly and is well connected so propagates a block rapidly. There is no other server, this is an extremely low budget pool. |
|
|
|
|
Show Posts
