[∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 24.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: jimjam123 on August 30, 2024, 03:49:49 AM

Quote from: -ck on August 29, 2024, 07:09:08 PM

Quote from: gparis on August 29, 2024, 06:39:38 PM

Why could I connect to another pool if it was my internet ? Working fine again this morning able to connect.

Because another pool would be routing through somewhere else. It's a routing issue somewhere between you and another point.

On a similar note, I recently sent a few machines to a mining facility in Kansas, and now having connecting issues to this pool.\
ITs 100% on them.
Is there another port?
Hate using another pool....
Thanks,

The ports are all on the same IP addresses so that won't change anything. What I suspect is happening is your DNS is defaulting to IPV6 if you support it and then failing. You can force either IPV6 or IPV4 by using solo6.ckpool.org or solo4.ckpool.org

willi9974

legendary

Activity: 3654

Merit: 3003

Top-tier crypto casino and sportsbook

Only the ports that are listet on the pool page --> https://solo.ckpool.org/

mybe you need a special firewall rule in your hosting location and ck pool is on a blacklist (from network view).

Can you open a shell and try a ping?

ping -4 solo.ckpool.org

Ping wird ausgeführt für solo.ckpool.org [51.81.56.15] mit 32 Bytes Daten:
Antwort von 51.81.56.15: Bytes=32 Zeit=103ms TTL=53
Antwort von 51.81.56.15: Bytes=32 Zeit=104ms TTL=53
Antwort von 51.81.56.15: Bytes=32 Zeit=104ms TTL=53
Antwort von 51.81.56.15: Bytes=32 Zeit=101ms TTL=53

jimjam123

member

Activity: 456

Merit: 16

Quote from: -ck on August 29, 2024, 07:09:08 PM

Quote from: gparis on August 29, 2024, 06:39:38 PM

Why could I connect to another pool if it was my internet ? Working fine again this morning able to connect.

Because another pool would be routing through somewhere else. It's a routing issue somewhere between you and another point.

On a similar note, I recently sent a few machines to a mining facility in Kansas, and now having connecting issues to this pool.\
ITs 100% on them.
Is there another port?
Hate using another pool....
Thanks,

gparis

newbie

Activity: 8

Merit: 0

Quote from: Sc0rPs on August 29, 2024, 07:53:28 PM

Quote from: gparis on August 29, 2024, 06:39:38 PM

Quote from: -ck on August 29, 2024, 06:30:21 PM

Quote from: gparis on August 29, 2024, 06:28:05 PM

I couldn't get on the pool yesterday tried different worker and still wouldn't let me on noticed that I couldn't connect for almost 18 hours, was anything wrong with the site ? I confirmed that there was nothing wrong with my miners by connecting to a different pool I will try ckpool again this morning strange that this happened on the day someone found a block ? Congratulations to them.

Pool's been fine, was probably some random internet connectivity issue between you and the pool.

Why could I connect to another pool if it was my internet ? Working fine again this morning able to connect.

You take different routes to different sites / pools or anything on the internet through various DHCP servers. There's always somewhere on the internet that you will not be able to connect to but will sooner or later. Next time try a full restart of your internet.

No problem thanks.

Sc0rPs

newbie

Activity: 22

Merit: 0

Quote from: buzzard34 on August 29, 2024, 04:37:09 PM

Quote from: -ck on August 29, 2024, 04:31:55 PM

Congratulations to miner 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT for solving the 291st solo block on solo.ckpool.org!

Code:

[2024-08-29 16:22:22.139] BLOCK ACCEPTED!
[2024-08-29 16:22:22.146] Solved and confirmed block 858978 by 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT.v32
[2024-08-29 16:22:22.146] User 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT:{"hashrate1m": "37.7P", "hashrate5m": "37.4P", "hashrate1hr": "36.4P", "hashrate1d": "40.1P", "hashrate7d": "22.8P", "shares": 18236962498882, "authorised": 1720833873}
[2024-08-29 16:22:22.146] Worker 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT.v32:{"hashrate1m": "28.4P", "hashrate5m": "27.5P", "hashrate1hr": "26.3P", "hashrate1d": "20.2P", "hashrate7d": "6.41P"}
[2024-08-29 16:22:22.198] Block solved after 81681463735017 shares at 91.3% diff

https://mempool.space/block/000000000000000000016ccd32328638865256249e592246bfae8af4031dda01

With 38PH this miner would solve a block on average once every ~4 months.

Looks like they took the rest of the day off

"hashrate1m": "0",
"hashrate5m": "0",
"hashrate1hr": "486T",
"hashrate1d": "33.3P",
"hashrate7d": "22.3P",
"lastshare": 1724952386,
"workers": 0,

Congrats to 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT!

May have been some heavy rented hash for a few hours noticing the pool luck was getting close to 100%, or figured lightning will not strike twice so move the rented hash elsewhere. Does look like it was being monitored by the miner.

Sc0rPs

newbie

Activity: 22

Merit: 0

Quote from: gparis on August 29, 2024, 06:39:38 PM

Quote from: -ck on August 29, 2024, 06:30:21 PM

Quote from: gparis on August 29, 2024, 06:28:05 PM

I couldn't get on the pool yesterday tried different worker and still wouldn't let me on noticed that I couldn't connect for almost 18 hours, was anything wrong with the site ? I confirmed that there was nothing wrong with my miners by connecting to a different pool I will try ckpool again this morning strange that this happened on the day someone found a block ? Congratulations to them.

Pool's been fine, was probably some random internet connectivity issue between you and the pool.

Why could I connect to another pool if it was my internet ? Working fine again this morning able to connect.

You take different routes to different sites / pools or anything on the internet through various DHCP servers. There's always somewhere on the internet that you will not be able to connect to but will sooner or later. Next time try a full restart of your internet.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: gparis on August 29, 2024, 06:39:38 PM

Why could I connect to another pool if it was my internet ? Working fine again this morning able to connect.

Because another pool would be routing through somewhere else. It's a routing issue somewhere between you and another point.

gparis

newbie

Activity: 8

Merit: 0

Quote from: -ck on August 29, 2024, 06:30:21 PM

Quote from: gparis on August 29, 2024, 06:28:05 PM

I couldn't get on the pool yesterday tried different worker and still wouldn't let me on noticed that I couldn't connect for almost 18 hours, was anything wrong with the site ? I confirmed that there was nothing wrong with my miners by connecting to a different pool I will try ckpool again this morning strange that this happened on the day someone found a block ? Congratulations to them.

Pool's been fine, was probably some random internet connectivity issue between you and the pool.

Why could I connect to another pool if it was my internet ? Working fine again this morning able to connect.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: gparis on August 29, 2024, 06:28:05 PM

I couldn't get on the pool yesterday tried different worker and still wouldn't let me on noticed that I couldn't connect for almost 18 hours, was anything wrong with the site ? I confirmed that there was nothing wrong with my miners by connecting to a different pool I will try ckpool again this morning strange that this happened on the day someone found a block ? Congratulations to them.

Pool's been fine, was probably some random internet connectivity issue between you and the pool.

gparis

newbie

Activity: 8

Merit: 0

I couldn't get on the pool yesterday tried different worker and still wouldn't let me on noticed that I couldn't connect for almost 18 hours, was anything wrong with the site ? I confirmed that there was nothing wrong with my miners by connecting to a different pool I will try ckpool again this morning strange that this happened on the day someone found a block ? Congratulations to them.

willi9974

legendary

Activity: 3654

Merit: 3003

Top-tier crypto casino and sportsbook

Or he mine with the next BTC address.

buzzard34

newbie

Activity: 13

Merit: 0

Quote from: -ck on August 29, 2024, 04:31:55 PM

Congratulations to miner 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT for solving the 291st solo block on solo.ckpool.org!

Code:

[2024-08-29 16:22:22.139] BLOCK ACCEPTED!
[2024-08-29 16:22:22.146] Solved and confirmed block 858978 by 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT.v32
[2024-08-29 16:22:22.146] User 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT:{"hashrate1m": "37.7P", "hashrate5m": "37.4P", "hashrate1hr": "36.4P", "hashrate1d": "40.1P", "hashrate7d": "22.8P", "shares": 18236962498882, "authorised": 1720833873}
[2024-08-29 16:22:22.146] Worker 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT.v32:{"hashrate1m": "28.4P", "hashrate5m": "27.5P", "hashrate1hr": "26.3P", "hashrate1d": "20.2P", "hashrate7d": "6.41P"}
[2024-08-29 16:22:22.198] Block solved after 81681463735017 shares at 91.3% diff

https://mempool.space/block/000000000000000000016ccd32328638865256249e592246bfae8af4031dda01

With 38PH this miner would solve a block on average once every ~4 months.

Looks like they took the rest of the day off

"hashrate1m": "0",
"hashrate5m": "0",
"hashrate1hr": "486T",
"hashrate1d": "33.3P",
"hashrate7d": "22.3P",
"lastshare": 1724952386,
"workers": 0,

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Congratulations to miner 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT for solving the 291st solo block on solo.ckpool.org!

Code:

[2024-08-29 16:22:22.139] BLOCK ACCEPTED!
[2024-08-29 16:22:22.146] Solved and confirmed block 858978 by 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT.v32
[2024-08-29 16:22:22.146] User 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT:{"hashrate1m": "37.7P", "hashrate5m": "37.4P", "hashrate1hr": "36.4P", "hashrate1d": "40.1P", "hashrate7d": "22.8P", "shares": 18236962498882, "authorised": 1720833873}
[2024-08-29 16:22:22.146] Worker 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT.v32:{"hashrate1m": "28.4P", "hashrate5m": "27.5P", "hashrate1hr": "26.3P", "hashrate1d": "20.2P", "hashrate7d": "6.41P"}
[2024-08-29 16:22:22.198] Block solved after 81681463735017 shares at 91.3% diff

https://mempool.space/block/000000000000000000016ccd32328638865256249e592246bfae8af4031dda01

With 38PH this miner would solve a block on average once every ~4 months.

Morguk

hero member

Activity: 595

Merit: 506

Congrats to the miner!

Looks like it was 40 Petahash?

o_solo_miner

legendary

Activity: 2483

Merit: 1482

-> morgen, ist heute, schon gestern <-

Congratulation to 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT for solving Block 858,978.

diff: 197522447695680 @ ~15-35P

blockhilltop

jr. member

Activity: 72

Merit: 3

Wow, congrats! Before 100% too

Bravo anon miner! Bravo CK & CK pool!

It's been a good year here for a handful of people.

ethanhunt2023

newbie

Activity: 13

Merit: 0

Congratulations!

Nexus9090

member

Activity: 259

Merit: 85

So many numbers and so little time

Well what do you know, looks like I spoke too soon Cheesy

Congratulations whoever found block 858978

Nexus9090

member

Activity: 259

Merit: 85

So many numbers and so little time

Far too quiet around here...

About time we hit another block don't you think?

ZukoIkeda

newbie

Activity: 1

Merit: 0

Hi all, new to mining. Sorry if this question is answered somewhere else but I saw conversations going back to 2014 and can't possibly read it all.
When solo mining with CK pool is there a way to verify which miner solved the block? What I'm trying to understand is if there is a way to verify if my miner finds a block. At this point (with limited understanding) I'm just point hash and CK pool and hoping they are trustworthy and will pay out if my miner gets lucky.

On a separate note is there a way to put a message in the found block? I see the last block (853742) from Solo CK pool and the coinbase tag and OP_RETURN data is full of gibberish. It would be cool if each solo miner could put their own notes in those fields (understandably this might mean more overhead for CK pool and if that's the reason why we can't that's totally fair).

Cheers!

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 24. (Read 108541 times)