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

[Flowingoaktree]

I recently bought a miner from China and read that somewhere that there is a possibility of a backdoor address if a block is found. Would that be possible and if so how would you test it?

[-ck]

I recently bought a miner from China and read that somewhere that there is a possibility of a backdoor address if a block is found. Would that be possible and if so how would you test it?

If you see the hashrate appearing under your address at the pool stats then it's impossible. If your hashrate doesn't show up or is less than it's supposed to be, it's possible.

[ethanhunt2023]

I recently bought a miner from China and read that somewhere that there is a possibility of a backdoor address if a block is found. Would that be possible and if so how would you test it?

What is the miner's name?

[-ck]

https://ausolostats.ckpool.org graphical stats for the AU solo ckpool are back online on a new separate server again courtesy of mineracks.com. Putting the stats on a separate server ensures optimal pool performance.

You may need to refresh the browser page to get the updated website, or your DNS caches may take a few minutes to update.

Mine on!

[imrbtc]

solo.ckpool.org had a drive issue and was down for 50 minutes. I've had to restart it with fresh storage so stats will be off.

is the nounce is also reset  like new fresh pool or it wil continue from where it left the efforts like its was 150+

[Flowingoaktree]

What is the miner's name?

Bitdsk but I think its a non issue

[ethanhunt2023]

What is the miner's name?

Bitdsk but I think its a non issue

It should be okay.

[-ck]

solo.ckpool.org had a drive issue and was down for 50 minutes. I've had to restart it with fresh storage so stats will be off.

is the nounce is also reset  like new fresh pool or it wil continue from where it left the efforts like its was 150+

It's not clear what you're asking but there is no progress with mining, only mining and not mining. There is no need to keep track of anything at all. Only the statistics are affected by the hard drive outage.

[willi9974]

USA Pool hits a Block
https://mempool.space/de/block/00000000000000000001457a4acc5da8e886dddd0a79a6899957a502e0a1977b

Concrats to the lucky solo miner --> 3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M
Sounds like a Bitaxe or so


Block 924569 (21.11.2025)
timestamp=21.11.2025 14:13:06
mediantime=21.11.2025 13:30:21
Net=152.271.405.447.597
Diff=221.386.883.580.799

https://solo.ckpool.org/users/3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M

Code:

{
 "hashrate1m": "6.09T",
 "hashrate5m": "5.77T",
 "hashrate1hr": "5.99T",
 "hashrate1d": "6.73T",
 "hashrate7d": "4.6T",
 "lastshare": 1763736988,
 "workers": 6,
 "shares": 1997476000,
 "bestshare": 221386883580799.4,
 "bestever": 221386883580799,
 "authorised": 1761432974,
 "worker": [
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.3",
   "hashrate1m": "1.49T",
   "hashrate5m": "1.25T",
   "hashrate1hr": "1.23T",
   "hashrate1d": "1.2T",
   "hashrate7d": "870G",
   "lastshare": 1763736987,
   "shares": 356008000,
   "bestshare": 221386883580799.4,
   "bestever": 221386883580799
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.6",
   "hashrate1m": "0",
   "hashrate5m": "0",
   "hashrate1hr": "45.8G",
   "hashrate1d": "907G",
   "hashrate7d": "585G",
   "lastshare": 1763725401,
   "shares": 247033000,
   "bestshare": 0.0,
   "bestever": 221866768
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.5",
   "hashrate1m": "993G",
   "hashrate5m": "1.04T",
   "hashrate1hr": "1.2T",
   "hashrate1d": "1.19T",
   "hashrate7d": "897G",
   "lastshare": 1763736986,
   "shares": 356034000,
   "bestshare": 310223.145274017,
   "bestever": 55842469
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.1",
   "hashrate1m": "938G",
   "hashrate5m": "1.09T",
   "hashrate1hr": "1.23T",
   "hashrate1d": "1.19T",
   "hashrate7d": "764G",
   "lastshare": 1763736988,
   "shares": 350142000,
   "bestshare": 269878330.7853546,
   "bestever": 376764932
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.2",
   "hashrate1m": "1.42T",
   "hashrate5m": "1.15T",
   "hashrate1hr": "1.08T",
   "hashrate1d": "1.04T",
   "hashrate7d": "707G",
   "lastshare": 1763736988,
   "shares": 333804000,
   "bestshare": 1059765.227528352,
   "bestever": 157682074
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.4",
   "hashrate1m": "1.51T",
   "hashrate5m": "1.3T",
   "hashrate1hr": "1.21T",
   "hashrate1d": "1.19T",
   "hashrate7d": "775G",
   "lastshare": 1763736983,
   "shares": 354455000,
   "bestshare": 1535217.818732429,
   "bestever": 1436921586
  }
 ]
}

holly shit, cracking a fucking block with a freaking small THs miner like a Bitaxe or so

   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.3",
   "hashrate1m": "1.49T",
   "hashrate5m": "1.25T",
   "hashrate1hr": "1.23T",
   "hashrate1d": "1.2T",
   "hashrate7d": "870G",
   "lastshare": 1763736987,
   "shares": 356008000,
   "bestshare": 221386883580799.4,
   "bestever": 221386883580799

First sean at 25. October 2025 on the solo pool and submittet only 1.997.476.000 shares in comparison of the actual diff from 152.271.405.447.597

1.997.476.000 / 152.271.405.447.597 ≈ 0,00000131   (0.00013%) of the expected value

https://solochance.com/
1,5 THs
Chance per block: 1 in 1,069,140,000
Chance per day: 1 in 7,424,583
Time estimate: 20,341 years

[Bitcoin-Pool]

USA Pool hits a Block
https://mempool.space/de/block/00000000000000000001457a4acc5da8e886dddd0a79a6899957a502e0a1977b

Concrats to the lucky solo miner --> 3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M
Sounds like a Bitaxe or so


Block 924569 (21.11.2025)
timestamp=21.11.2025 14:13:06
mediantime=21.11.2025 13:30:21
Net=152.271.405.447.597
Diff=221.386.883.580.799

https://solo.ckpool.org/users/3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M

Code:

{
 "hashrate1m": "6.09T",
 "hashrate5m": "5.77T",
 "hashrate1hr": "5.99T",
 "hashrate1d": "6.73T",
 "hashrate7d": "4.6T",
 "lastshare": 1763736988,
 "workers": 6,
 "shares": 1997476000,
 "bestshare": 221386883580799.4,
 "bestever": 221386883580799,
 "authorised": 1761432974,
 "worker": [
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.3",
   "hashrate1m": "1.49T",
   "hashrate5m": "1.25T",
   "hashrate1hr": "1.23T",
   "hashrate1d": "1.2T",
   "hashrate7d": "870G",
   "lastshare": 1763736987,
   "shares": 356008000,
   "bestshare": 221386883580799.4,
   "bestever": 221386883580799
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.6",
   "hashrate1m": "0",
   "hashrate5m": "0",
   "hashrate1hr": "45.8G",
   "hashrate1d": "907G",
   "hashrate7d": "585G",
   "lastshare": 1763725401,
   "shares": 247033000,
   "bestshare": 0.0,
   "bestever": 221866768
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.5",
   "hashrate1m": "993G",
   "hashrate5m": "1.04T",
   "hashrate1hr": "1.2T",
   "hashrate1d": "1.19T",
   "hashrate7d": "897G",
   "lastshare": 1763736986,
   "shares": 356034000,
   "bestshare": 310223.145274017,
   "bestever": 55842469
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.1",
   "hashrate1m": "938G",
   "hashrate5m": "1.09T",
   "hashrate1hr": "1.23T",
   "hashrate1d": "1.19T",
   "hashrate7d": "764G",
   "lastshare": 1763736988,
   "shares": 350142000,
   "bestshare": 269878330.7853546,
   "bestever": 376764932
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.2",
   "hashrate1m": "1.42T",
   "hashrate5m": "1.15T",
   "hashrate1hr": "1.08T",
   "hashrate1d": "1.04T",
   "hashrate7d": "707G",
   "lastshare": 1763736988,
   "shares": 333804000,
   "bestshare": 1059765.227528352,
   "bestever": 157682074
  },
  {
   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.4",
   "hashrate1m": "1.51T",
   "hashrate5m": "1.3T",
   "hashrate1hr": "1.21T",
   "hashrate1d": "1.19T",
   "hashrate7d": "775G",
   "lastshare": 1763736983,
   "shares": 354455000,
   "bestshare": 1535217.818732429,
   "bestever": 1436921586
  }
 ]
}

holly shit, cracking a fucking block with a freaking small THs miner like a Bitaxe or so

   "workername": "3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.3",
   "hashrate1m": "1.49T",
   "hashrate5m": "1.25T",
   "hashrate1hr": "1.23T",
   "hashrate1d": "1.2T",
   "hashrate7d": "870G",
   "lastshare": 1763736987,
   "shares": 356008000,
   "bestshare": 221386883580799.4,
   "bestever": 221386883580799

First sean at 25. October 2025 on the solo pool and submittet only 1.997.476.000 shares in comparison of the actual diff from 152.271.405.447.597

1.997.476.000 / 152.271.405.447.597 ≈ 0,00000131   (0.00013%) of the expected value

https://solochance.com/
1,5 THs
Chance per block: 1 in 1,069,140,000
Chance per day: 1 in 7,424,583
Time estimate: 20,341 years

That's incredible! The device itself that found the block, presumably a 1370 chip, only delivered 360 million shares.

Congratulations to the finder who wasn't even mining for two weeks!

[-ck]

Congratulations to extremely lucky miner 3K99~Ct8M with only SIX TH for solving the 308th solo block at http://solo.ckpool.org. A miner of this size has only a a in 1.2 million chance of solving a block each day!

Code:

[2025-11-21 14:13:37.391] Possible block solve diff 221386883580799.375000 !
[2025-11-21 14:13:37.459] BLOCK ACCEPTED!
[2025-11-21 14:13:37.462] Solved and confirmed block 924569 by 3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.3
[2025-11-21 14:13:37.462] User 3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M:{"hashrate1m": "6.02T", "hashrate5m": "6.01T", "hashrate1hr": "6.13T", "hashrate1d": "6.75T", "hashrate7d": "4.59T", "shares": 1993962000, "authorised": 1761432974}
[2025-11-21 14:13:37.462] Worker 3K99ATGytaz1Ns2xNiJfjQbECz5ewnCt8M.3:{"hashrate1m": "1.26T", "hashrate5m": "1.22T", "hashrate1hr": "1.23T", "hashrate1d": "1.19T", "hashrate7d": "869G"}

https://mempool.space/block/00000000000000000001457a4acc5da8e886dddd0a79a6899957a502e0a1977b

[philipma1957]

that address seems familiar maybe this person hit a block a while back.  I could be wrong.

but it is still a nice hit even if I am wrong.

[1KKF]

Hello, my hashrate is significantly lower than it actually is. Is this a bug or is this normal? I'm using 6 S21XP 270Th miners for a solo win. Electricity is very expensive, $34 per day, but I'm hoping for luck.

 "hashrate1m": "1.14P",
 "hashrate5m": "902T",
 "hashrate1hr": "891T",
 "hashrate1d": "678T",
 "hashrate7d": "165T",
 "lastshare": 1763903118,
 "workers": 34,
 "shares": 25826310000,
 "bestshare": 70010352442.94943,
 "bestever": 70010352442,
 "authorised": 1761442766,
 

[Nexus9090]

Hello, my hashrate is significantly lower than it actually is. Is this a bug or is this normal? I'm using 6 S21XP 270Th miners for a solo win. Electricity is very expensive, $34 per day, but I'm hoping for luck.

 "hashrate1m": "1.14P",
 "hashrate5m": "902T",
 "hashrate1hr": "891T",
 "hashrate1d": "678T",
 "hashrate7d": "165T",
 "lastshare": 1763903118,
 "workers": 34,
 "shares": 25826310000,
 "bestshare": 70010352442.94943,
 "bestever": 70010352442,
 "authorised": 1761442766,
 

Hash rate is variable and averaged, it looks like you've not been running for very long, so the averages will be low.

Let it run for a few days then the reported hash rates will be more inline with your rigs actual performance.

[philipma1957]

Hello, my hashrate is significantly lower than it actually is. Is this a bug or is this normal? I'm using 6 S21XP 270Th miners for a solo win. Electricity is very expensive, $34 per day, but I'm hoping for luck.

 "hashrate1m": "1.14P",
 "hashrate5m": "902T",
 "hashrate1hr": "891T",
 "hashrate1d": "678T",
 "hashrate7d": "165T",
 "lastshare": 1763903118,
 "workers": 34,
 "shares": 25826310000,
 "bestshare": 70010352442.94943,
 "bestever": 70010352442,
 "authorised": 1761442766,
 

you should do 1.6p

so post your numbers in a few hours so we can see if they go up.

[88nE6w2xfri6izL1Xx239ELXb]

To the Con Kolivas / ckpool Developer Team,

I am writing to report a specific change observed in the latest version of the ckpool source code (Copyright 2025) compared to the previous version (Copyright 2023).

Upon analyzing the source code, specifically stratifier.c, I noticed that the LOGNOTICE call responsible for logging the hash of a solved block has been removed.

1. Technical Detail:

File: stratifier.c

Function: test_blocksolve()

Location: Immediately following the local_block_submit() call.

2. The Change: In the previous version (2023), the code included the following logging statement when a block was successfully submitted:

C

if (ret) {
    LOGNOTICE("Proof of Work found with hash %s", blockhash);
    // ...
}
In the current version (2025), this specific LOGNOTICE line appears to be missing. The code now submits the block and proceeds directly to share logging without outputting the block hash to the main pool log.

3. Impact: This specific log entry is critical for pool operators. It provides immediate, visible confirmation in the standard logs that a block has been found and solved by the pool. Removing this line makes it significantly harder to monitor successful block solves in real-time and complicates the verification process without querying the daemon directly.

4. Request: Could you please clarify if this removal was intentional?

If this was an oversight: I kindly request that this logging statement be restored in the next release to maintain feature parity with previous versions.

If this was intentional: Could you please explain the reasoning behind suppressing this output? Understanding the rationale would be very helpful for pool administration.

Thank you for your time and for your continued work on this project.

[-ck]

To the Con Kolivas / ckpool Developer Team,

I am writing to report a specific change observed in the latest version of the ckpool source code (Copyright 2025) compared to the previous version (Copyright 2023).

Upon analyzing the source code, specifically stratifier.c, I noticed that the LOGNOTICE call responsible for logging the hash of a solved block has been removed.

1. Technical Detail:

File: stratifier.c

Function: test_blocksolve()

Location: Immediately following the local_block_submit() call.

2. The Change: In the previous version (2023), the code included the following logging statement when a block was successfully submitted:

C

if (ret) {
    LOGNOTICE("Proof of Work found with hash %s", blockhash);
    // ...
}
In the current version (2025), this specific LOGNOTICE line appears to be missing. The code now submits the block and proceeds directly to share logging without outputting the block hash to the main pool log.

3. Impact: This specific log entry is critical for pool operators. It provides immediate, visible confirmation in the standard logs that a block has been found and solved by the pool. Removing this line makes it significantly harder to monitor successful block solves in real-time and complicates the verification process without querying the daemon directly.

4. Request: Could you please clarify if this removal was intentional?

If this was an oversight: I kindly request that this logging statement be restored in the next release to maintain feature parity with previous versions.

If this was intentional: Could you please explain the reasoning behind suppressing this output? Understanding the rationale would be very helpful for pool administration.

Thank you for your time and for your continued work on this project.

As I haven't maintained a shared pool in almost a decade, it was probably just an oversight as part of some other clean up. Submit a pull request to have the code reinstated.

[caijh369]

How can one verify whether the computing power of a BTC mining machine is valid? Does it mean that if we can see the computing power on the website, then this computing power is valid and we can potentially mine a block?

[-ck]

How can one verify whether the computing power of a BTC mining machine is valid? Does it mean that if we can see the computing power on the website, then this computing power is valid and we can potentially mine a block?

Yes, hashrate cannot be faked at the pool end. If the pool shows a hashrate close to the hardware's specifications then it is valid.

[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.