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
https://btc.com/btc/block/721310
|
|
|
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.
|
|
|
HOLY SHIT!!!!! Just waking up and seeing that my GekkoScience Compac F USB stick farm just hit The OMEN has 9 of these little Compac F guys running on it. HOLY SHIT!!!!!! CK thank you for running your pool. I need coffee!!! Haha, congrats!
|
|
|
Congratulations to 3EoqjNmeaaVvVDCPbVXxQQRH6UFpDUqpPg ! [2022-01-24 11:59:25.325] Possible block solve diff 35503405521727.414062 ! [2022-01-24 11:59:25.403] BLOCK ACCEPTED! [2022-01-24 11:59:25.405] Solved and confirmed block 720175 by 3EoqjNmeaaVvVDCPbVXxQQRH6UFpDUqpPg.TheOmen [2022-01-24 11:59:25.405] User 3EoqjNmeaaVvVDCPbVXxQQRH6UFpDUqpPg:{"hashrate1m": "8.31T", "hashrate5m": "8.33T", "hashrate1hr": "8.54T", "hashrate1d": "8.9T", "hashrate7d": "86.5T"} [2022-01-24 11:59:25.405] Worker 3EoqjNmeaaVvVDCPbVXxQQRH6UFpDUqpPg.TheOmen:{"hashrate1m": "3.65T", "hashrate5m": "3.25T", "hashrate1hr": "3.32T", "hashrate1d": "3.41T", "hashrate7d": "2.49T"} [2022-01-24 11:59:25.441] Block solved after 6987442893887 shares at 26.2% diff
https://btc.com/btc/block/720175
|
|
|
If I give both miners the same BTC address, what happens?
I mean: (Mineadr) 38HRDQeecdfQnCyrnLEtKJGnEsrLG3XUCt
38HRDQeecdfQnCyrnLEtKJGnEsrLG3XUCt
Without a period at the end as you said and without differentiating one from the other, can something happen?
No harm at all, the hashrate just shows as one combined amount.
|
|
|
Is bech32 supported? Are there any limitations on the address types used for account and payout?
All 1x and 3x addresses and bech32 are supported, bech32m has not yet been validated.
|
|
|
Please stay on topic. It's plain fucking rude to promote another pool in this thread. It's also not a support thread for anything unrelated to mining here directly or indirectly. Carry on.
|
|
|
Incredible, another small miner! Hasn't even been mining a week! [2022-01-13 00:34:43.185] Possible block solve diff 33707998008435.707031 ! [2022-01-13 00:34:43.239] BLOCK ACCEPTED! [2022-01-13 00:34:43.242] Solved and confirmed block 718379 by 38HRDQeecdfQnCyrnLEtKJGnEsrLG3XUCt [2022-01-13 00:34:43.242] User 38HRDQeecdfQnCyrnLEtKJGnEsrLG3XUCt:{"hashrate1m": "116T", "hashrate5m": "113T", "hashrate1hr": "110T", "hashrate1d": "73.4T", "hashrate7d": "15.9T"} [2022-01-13 00:34:43.242] Worker 38HRDQeecdfQnCyrnLEtKJGnEsrLG3XUCt:{"hashrate1m": "116T", "hashrate5m": "113T", "hashrate1hr": "110T", "hashrate1d": "73.4T", "hashrate7d": "15.9T"} [2022-01-13 00:34:43.283] Block solved after 1167821067490 shares at 4.8% diff
https://btc.com/btc/block/718379I've since confirmed in the logs that this miner joined less than 2 days ago, presumably in response to seeing the other lucky solo miner block solve, so they've been astronomically lucky.
|
|
|
Incredible, another small miner! Hasn't even been mining a week! [2022-01-13 00:34:43.185] Possible block solve diff 33707998008435.707031 ! [2022-01-13 00:34:43.239] BLOCK ACCEPTED! [2022-01-13 00:34:43.242] Solved and confirmed block 718379 by 38HRDQeecdfQnCyrnLEtKJGnEsrLG3XUCt [2022-01-13 00:34:43.242] User 38HRDQeecdfQnCyrnLEtKJGnEsrLG3XUCt:{"hashrate1m": "116T", "hashrate5m": "113T", "hashrate1hr": "110T", "hashrate1d": "73.4T", "hashrate7d": "15.9T"} [2022-01-13 00:34:43.242] Worker 38HRDQeecdfQnCyrnLEtKJGnEsrLG3XUCt:{"hashrate1m": "116T", "hashrate5m": "113T", "hashrate1hr": "110T", "hashrate1d": "73.4T", "hashrate7d": "15.9T"} [2022-01-13 00:34:43.283] Block solved after 1167821067490 shares at 4.8% diff
https://btc.com/btc/block/718379
|
|
|
Congratulations to 17zBdPyqq42RMjtHxH5DTx2uRTy4DsmrFw and great to see the low hashrate what hit this block!
As far as I can see, unless they recently changed addresses, they only had 126TH onboard.
|
|
|
|