[∞ YH] US/EU/AU solo.ckpool.org 2% fee solo mining 311 blocks solved!

[Josek8]

Hello.

I've been seeing several errors lately on Ckpool:

1.- I'm trying to access the URL where I can enter my wallet address to see the status of the ASICs, but it doesn't show up on Google.
On my computer, my antivirus pops up when I try to access it.

2.- I'm trying to connect to CKPOOL with two miners and it's impossible. On Viabtc it works perfectly, I can see them and the hashrate is normal, but on CKpool it's impossible.

I've ordered a new router to see if that might be the problem, but if you could check if other users are experiencing the same issue, that would be great.

Thank you very much.

[itrider]

Functionally, I agree it’s minor: the rejects are low-value shares and the window is short. I only want to flag it for ck because it spikes the reported reject metric when it happens on a high-vardiff miner, even though nothing is actually wrong.

If this is intended (new diff applies on next notify/job only) then all good; if not, perhaps forcing an immediate notify when adjusting diff after an idle/reconnect would keep server and miner in sync and avoid the temporary “high diff …/old_diff” burst.

Here's the protocol documentation linked that describes new diff, which is meant to apply to the next notify. Mining hardware and other software may have not implemented it this way, but ckpool has.
https://bitcointalk.org/index.php?topic=557866.msg6078264#msg6078264

https://bitbucket.org/ckolivas/ckpool/commits/3a6da1fafcb8a291e188b0ea4b1f12ddcd962395

Thanks ck, great patch, and thanks for implementing the fix 😉👍

[Nexus9090]

Hello.

I've been seeing several errors lately on Ckpool:

1.- I'm trying to access the URL where I can enter my wallet address to see the status of the ASICs, but it doesn't show up on Google.
On my computer, my antivirus pops up when I try to access it.

2.- I'm trying to connect to CKPOOL with two miners and it's impossible. On Viabtc it works perfectly, I can see them and the hashrate is normal, but on CKpool it's impossible.

I've ordered a new router to see if that might be the problem, but if you could check if other users are experiencing the same issue, that would be great.

Thank you very much.

Some anti-virus software falsely reports solo.ckpool.org/users/your-btc-address as malicious.

In a recent update to Norton anti-virus it has started doing this. So, its more likely that your anti-virus software is preventing access than anything else.

Instead of using the text based report, you can access the chart based reports https://stats.ckpool.org/users/yout-btc-address


On the topic of connecting multiple miners to the pool, each miner needs to be given its own name as an extension to your btc address.

For example:-

3MbtxahpbkC1fGhvcWR7Ja38u8cwN9wzY8.worker1
3MbtxahpbkC1fGhvcWR7Ja38u8cwN9wzY8.worker2
3MbtxahpbkC1fGhvcWR7Ja38u8cwN9wzY8.worker3

or

3MbtxahpbkC1fGhvcWR7Ja38u8cwN9wzY8_worker1
3MbtxahpbkC1fGhvcWR7Ja38u8cwN9wzY8_worker2
3MbtxahpbkC1fGhvcWR7Ja38u8cwN9wzY8_worker3


accessing the chart stats is then be through your btc address E.g.    https://stats.ckpool.org/users/3MbtxahpbkC1fGhvcWR7Ja38u8cwN9wzY8

[willi9974]

cracked a other block

https://mempool.space/de/block/00000000000000000000a8e30a009cd15c7c8ee207cfc352eac02e653e182ba5

https://solo.ckpool.org/users/bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n


  "workername": "bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n.W02",
   "hashrate1m": "151T",
   "hashrate5m": "138T",
   "hashrate1hr": "144T",
   "hashrate1d": "138T",
   "hashrate7d": "137T",
   "lastshare": 1764235583,
   "shares": 90911430690,
   "bestshare": 426655393281336.0,
   "bestever": 426655393281336

Code:

{
 "hashrate1m": "722T",
 "hashrate5m": "682T",
 "hashrate1hr": "693T",
 "hashrate1d": "695T",
 "hashrate7d": "691T",
 "lastshare": 1764235583,
 "workers": 5,
 "shares": 458582415710,
 "bestshare": 426655393281336.0,
 "bestever": 426655393281336,
 "authorised": 1761432964,
 "worker": [
  {
   "workername": "bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n.W01",
   "hashrate1m": "172T",
   "hashrate5m": "155T",
   "hashrate1hr": "140T",
   "hashrate1d": "140T",
   "hashrate7d": "140T",
   "lastshare": 1764235583,
   "shares": 92733885354,
   "bestshare": 227009935.2115344,
   "bestever": 44961865162
  },
  {
   "workername": "bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n.W05",
   "hashrate1m": "144T",
   "hashrate5m": "128T",
   "hashrate1hr": "131T",
   "hashrate1d": "138T",
   "hashrate7d": "137T",
   "lastshare": 1764235580,
   "shares": 90615718124,
   "bestshare": 182862496.0332989,
   "bestever": 197608952188
  },
  {
   "workername": "bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n.W04",
   "hashrate1m": "149T",
   "hashrate5m": "131T",
   "hashrate1hr": "139T",
   "hashrate1d": "142T",
   "hashrate7d": "139T",
   "lastshare": 1764235582,
   "shares": 92421995444,
   "bestshare": 681732967.8573561,
   "bestever": 172354710274
  },
  {
   "workername": "bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n.W02",
   "hashrate1m": "151T",
   "hashrate5m": "138T",
   "hashrate1hr": "144T",
   "hashrate1d": "138T",
   "hashrate7d": "137T",
   "lastshare": 1764235583,
   "shares": 90911430690,
   "bestshare": 426655393281336.0,
   "bestever": 426655393281336
  },
  {
   "workername": "bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n.W03",
   "hashrate1m": "122T",
   "hashrate5m": "135T",
   "hashrate1hr": "139T",
   "hashrate1d": "138T",
   "hashrate7d": "138T",
   "lastshare": 1764235580,
   "shares": 91899386098,
   "bestshare": 42143837.65803428,
   "bestever": 40514366131
  }
 ]
}

[-ck]

Congratulations to miner bc1q~xv9n with ~700TH for solving the 309th solo block at solo.ckpool.org! A miner of this size has a 1 in 10,000 chance of solving a block each day.

Code:

[2025-11-27 07:20:01.630] Possible block solve diff 426655393281336.000000 !
[2025-11-27 07:20:01.712] BLOCK ACCEPTED!
[2025-11-27 07:20:01.717] Solved and confirmed block 925380 by bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n.W02
[2025-11-27 07:20:01.718] User bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n:{"hashrate1m": "663T", "hashrate5m": "680T", "hashrate1hr": "702T", "hashrate1d": "695T", "hashrate7d": "691T", "shares": 457355918326, "authorised": 1761432964}
[2025-11-27 07:20:01.718] Worker bc1qacpq78zz9m4knzmg7g93crm7pp0q57weetxv9n.W02:{"hashrate1m": "143T", "hashrate5m": "147T", "hashrate1hr": "143T", "hashrate1d": "137T", "hashrate7d": "137T"}
[2025-11-27 07:20:01.729] Block solved after 24015069758051 shares at 16.1% diff

https://mempool.space/block/00000000000000000000a8e30a009cd15c7c8ee207cfc352eac02e653e182ba5

[blockhilltop]

Wow! Two relatively small (one very small) miners in one week, major congrats!

After a cool spell, the US pool is hot, wonder who's next, EU? Or Au? and when!? EU is over 101%!

Bravo CK and to the two lucky miners! I'm sure I speak for many here when I say I just wish it were me this time (for a change)

[Jg72]

Hey All

I had a couple of Bitaxes running on CK for over a year. Then I started to try other coins on other pools.

When I tried switching back to CK none of my miners will connect.

Not sure why. Anybody have any ideas?

https://imgur.com/a/HnIQxWr

[Bitcoin-Pool]

Hey All

I had a couple of Bitaxes running on CK for over a year. Then I started to try other coins on other pools.

When I tried switching back to CK none of my miners will connect.

Not sure why. Anybody have any ideas?

for sure wrong settings in your bitaxe

[Jg72]

Hey All

I had a couple of Bitaxes running on CK for over a year. Then I started to try other coins on other pools.

When I tried switching back to CK none of my miners will connect.

Not sure why. Anybody have any ideas?

https://imgur.com/a/HnIQxWr

for sure wrong settings in your bitaxe

Host: solo.ckpool.org
Port:  3333
-Wallet addy-
Pass: X

This is what I’m putting in.

[-ck]

Hey All

I had a couple of Bitaxes running on CK for over a year. Then I started to try other coins on other pools.

When I tried switching back to CK none of my miners will connect.

Not sure why. Anybody have any ideas?

for sure wrong settings in your bitaxe

Host: solo.ckpool.org
Port:  3333
-Wallet addy-
Pass: X

This is what I’m putting in.

Invalid wallet address most likely explanation (some interfaces allow you to put a space in which makes it invalid.)

[Jg72]

Hey All

I had a couple of Bitaxes running on CK for over a year. Then I started to try other coins on other pools.

When I tried switching back to CK none of my miners will connect.

Not sure why. Anybody have any ideas?

https://imgur.com/a/HnIQxWr

for sure wrong settings in your bitaxe

Host: solo.ckpool.org
Port:  3333
-Wallet addy-
Pass: X

This is what I’m putting in.

Invalid wallet address most likely explanation (some interfaces allow you to put a space in which makes it invalid.)

So I selected the host field and typed “eu” in front of solo and it works. Remove “eu” and connection fails. No other changes.

Wallet address is good.

[Jg72]

Hey All

I had a couple of Bitaxes running on CK for over a year. Then I started to try other coins on other pools.

When I tried switching back to CK none of my miners will connect.

Not sure why. Anybody have any ideas?

https://imgur.com/a/HnIQxWr

for sure wrong settings in your bitaxe

Host: solo.ckpool.org
Port:  3333
-Wallet addy-
Pass: X

This is what I’m putting in.

Invalid wallet address most likely explanation (some interfaces allow you to put a space in which makes it invalid.)

So I selected the host field and typed “eu” in front of solo and it works. Remove “eu” and connection fails. No other changes.

Wallet address is good.

Apparently it’s a router issue that is only affecting CK and it’s happening intermittently. Fun times.

[willi9974]

a new block on the EU solo pool

https://mempool.space/de/block/0000000000000000000128b8e814ce04f8b9b61ef4485023028afebfcf6bb4a8

https://mempool.space/de/address/bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj
https://eusolo.ckpool.org/users/bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj

 "workername": "bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj.Q2",
   "hashrate1m": "94.1T",
   "hashrate5m": "92.3T",
   "hashrate1hr": "91.9T",
   "hashrate1d": "92.6T",
   "hashrate7d": "49T",
   "lastshare": 1764459452,
   "shares": 9961551337,
   "bestshare": 242841527731792.5,
   "bestever": 242841527731792

Code:

{
 "hashrate1m": "160T",
 "hashrate5m": "176T",
 "hashrate1hr": "190T",
 "hashrate1d": "192T",
 "hashrate7d": "104T",
 "lastshare": 1764459454,
 "workers": 3,
 "shares": 24761857974,
 "bestshare": 242841527731792.5,
 "bestever": 242841527731792,
 "authorised": 1759853223,
 "worker": [
  {
   "workername": "bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj.Q3",
   "hashrate1m": "0",
   "hashrate5m": "0",
   "hashrate1hr": "0",
   "hashrate1d": "5.11G",
   "hashrate7d": "387G",
   "lastshare": 1764265385,
   "shares": 1463390224,
   "bestshare": 0.0,
   "bestever": 4810406478
  },
  {
   "workername": "bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj.Q1",
   "hashrate1m": "64T",
   "hashrate5m": "80.2T",
   "hashrate1hr": "93.1T",
   "hashrate1d": "94.8T",
   "hashrate7d": "52.2T",
   "lastshare": 1764459454,
   "shares": 12821442573,
   "bestshare": 1752667623.609547,
   "bestever": 5196460551
  },
  {
   "workername": "bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj.Nerdaxe",
   "hashrate1m": "5.95T",
   "hashrate5m": "4.79T",
   "hashrate1hr": "4.8T",
   "hashrate1d": "4.8T",
   "hashrate7d": "2.54T",
   "lastshare": 1764459446,
   "shares": 515473840,
   "bestshare": 15747697.9602446,
   "bestever": 219028504
  },
  {
   "workername": "bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj.Q2",
   "hashrate1m": "94.1T",
   "hashrate5m": "92.3T",
   "hashrate1hr": "91.9T",
   "hashrate1d": "92.6T",
   "hashrate7d": "49T",
   "lastshare": 1764459452,
   "shares": 9961551337,
   "bestshare": 242841527731792.5,
   "bestever": 242841527731792
  }
 ]
}

[-ck]

Congratulations to miner bc1q~aalj with ~200TH for solving the 310th solo block on the http://eusolo.ckpool.org server! 

Code:

[2025-11-29 22:10:57.619] Possible block solve diff 242841527731792.468750 !
[2025-11-29 22:10:57.685] BLOCK ACCEPTED!
[2025-11-29 22:10:57.688] Solved and confirmed block 925758 by bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj.Q2
[2025-11-29 22:10:57.688] User bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj:{"hashrate1m": "199T", "hashrate5m": "195T", "hashrate1hr": "199T", "hashrate1d": "192T", "hashrate7d": "103T", "shares": 24530181833, "authorised": 1759853223}
[2025-11-29 22:10:57.688] Worker bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj.Q2:{"hashrate1m": "110T", "hashrate5m": "95.2T", "hashrate1hr": "97.7T", "hashrate1d": "92.7T", "hashrate7d": "48.6T"}
[2025-11-29 22:10:57.692] Block solved after 154866698300670 shares at 103.7% diff

A miner of this size has a 1 in ~35K chance of solving a block each day.

[buzzard34]

a new block on the EU solo pool

https://mempool.space/de/block/0000000000000000000128b8e814ce04f8b9b61ef4485023028afebfcf6bb4a8

https://mempool.space/de/address/bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj
https://eusolo.ckpool.org/users/bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj

 "workername": "bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj.Q2",
   "hashrate1m": "94.1T",
   "hashrate5m": "92.3T",
   "hashrate1hr": "91.9T",
   "hashrate1d": "92.6T",
   "hashrate7d": "49T",
   "lastshare": 1764459452,
   "shares": 9961551337,
   "bestshare": 242841527731792.5,
   "bestever": 242841527731792

Looks like it may have been an Avalon Q. Score one for the home miner!

[o_solo_miner]

Congratulations to miner bc1qdtcw7jvsucw6ett6vdz3cm3a4eqq9y6n5kaalj for solving block 925758.

2 Blocks in a short time, impressiv.

[Predator112]

Please tell me the current settings for the Russian Federation; not all the hashrate is reaching me.

[sunds77]

Is there any suitable solo pool for China? Eusolo.ckpool.org has the lowest latency among the three pools, but still has 200ms. Is this latency invalid for solo BTC? How can I improve the connection speed? Thanks

[Ditbick]

Is there any suitable solo pool for China? Eusolo.ckpool.org has the lowest latency among the three pools, but still has 200ms. Is this latency invalid for solo BTC? How can I improve the connection speed? Thanks

Check viabtc or kanopool ... both of them offers solo mining option.

[sunds77]

Is there any suitable solo pool for China? Eusolo.ckpool.org has the lowest latency among the three pools, but still has 200ms. Is this latency invalid for solo BTC? How can I improve the connection speed? Thanks

Check viabtc or kanopool ... both of them offers solo mining option.

I have tried many pools, and the latency of eusolo.ckpool.org and solohash.co.uk is the lowest, about 190ms-210ms, while most others are above 300ms. I would like to inquire whether a 200ms latency can make solo work properly?