New to mining to help do my part and my first post!
Big shout out to CK - honestly love what you're doing! Amazing
My story - my first mining setup at Canaan Avalon Miner Q 1x 90th asic and 2 x bitaxes to start off on my own node and local ckpool running on a dedicated powerful server for a bit of fun
For this setup: 1) What is the best - min/start diff in ckpool.conf give my 3 miners (90th and 2 x 1th) 2) Best update_interval in seconds? is lower like better but I think it caps at 10 seconds? As Create new block logs shows 10 seconds no matter how low i set it 3) Optimized nonce1legnth and nonce2length? given my hashrate above 4) Is it better to have my bitaxe on another server to split it if it impacts SPS?
Here are my stats from logs: {"hashrate1m":"80.6T","hashrate5m":"84.7T","hashrate1hr":"82.4T","hashrate1d":"81T","hashrate7d":"54.3T","lastshare":1752402374,"workers":3,"shares":12851087015,"bestshare":22628632347.360809,"bestever":22628632347,"authorised":1751685205} [2025-07-13 11:26:16.033] Pool:{"diff": 0.01, "accepted": 12851087015, "rejected": 23557258, "bestshare": 22628632347, "SPS1m": 0.732, "SPS5m": 0.72, "SPS15m": 0.737, "SPS1h": 0.743} [2025-07-13 11:26:23.145] Stored local workbase with 348 transactions [2025-07-13 11:26:53.147] Stored local workbase with 381 transactions
Is there any maths to above, I am a numbers guy
Dicking with those settings achieves nothing unless something's not working. Leave them at defaults. The only thing to make sure is that you have ZMQ set up as per the solomining readme.
Once again this is another standalone pool like the EU variant, but will share the solo.ckpool.org coinbase signature on any blocks solved.
The new ausolo ckpool is chugging along nicely with just over 50 users. It has peaked above 15PH at one stage, but is hovering below 1PH for now, which is not entirely unexpected.
I've been informed that due to routing from Brisbane, some parts of Asia are not well connected to the pool, so I recommend checking your ping times if you're in Asia to see which of the 3 solo ckpools services you best. The EU server is located in Germany and the main pool is in west coast USA, so it could be any depending on your location. The lowest ping times will determine which server is best for you.
Also note again that each pool is standalone and that you need to check the stats on the pool you're on as they're not shared.
[2025-07-10 23:23:41.679] Solved and confirmed block 904989 by 35nyBqH57y7i7diofDiAGRsBDPrSEuzePa.v53
What is the reason to use a legacy BTC address?
Many people have wallets that predate native segwit support being widespread, and/or may have set up a multisig address using the legacy format. In addition, 3x addresses can simply be wrapped segwit addresses chosen for maximum compatibility with older wallets. Some custodial wallets default to this format for that reason.
Absolutely. As long as a miner is fast enough to process at least 1 share before the next block is found (on avg every 10 min) and work is reset, there is always a chance.
You don't even need to process 1 share on average, you just need to process at least one hash before the longest possible block solve period which is probably around 2 hours. The chance is of course astronomically low, but it's theoretically possible, just unrealistic.
Post
Topic
BoardPools
[BLOCK] solo.ckpool.org 2% fee solo mining 302 blocks solved!
by
-ck
on 11/07/2025, 00:01:11 UTC
Congratulations to miner 35ny~zePa with an enormous 200PH for solving the 302nd solo block solved at https://solo.ckpool.org!
A block party is being held this weekend with an estimated up to 7EH where you can contribute your own hash or buy hash if anyone's interested: https://upendo.rigly.io/
I am using an apollo futurebit running its own node to solo mine to. I see that it uses ckpool. I can not find my stats when visiting the ckpool stats using my btc address. Is there a a way to view my stats on ckpool when using a futurebit apollo 2?
No, because you're running it locally. You can mine to this solo pool directly to see stats here, but that defeats the purpose of having a miner that solo mines to itself.
Philip created this video for setting up your own solo pool, but it was not for Pi OS per se: https://www.youtube.com/watch?v=dAa6PkVN-3o Check for updated README-SOLOMINING instructions on the ckpool git repository, as it shows how to configure it for bitcoin core versions 28 and later.
I will be restarting both pools within the next hour for trivial ckpool updates and bitcoin daemon updates. Downtime should be minimal, but make sure to have a backup pool specified.
Both pools have now been updated and restarted. Mine on!
This update made ckpool continue to age and update stats of users and workers that have gone idle for long periods for the stats to be accurate for intermittent or stopped miners, and has updated the bitcoin daemon to version 29.0.
I will be restarting both pools within the next hour for trivial ckpool updates and bitcoin daemon updates. Downtime should be minimal, but make sure to have a backup pool specified.
Both pools have now been updated and restarted. Mine on!
I will be restarting both pools within the next hour for trivial ckpool updates and bitcoin daemon updates. Downtime should be minimal, but make sure to have a backup pool specified.
The best share was found since the last block find as I try reset each time so the best share of 600m should be showing on the pool.
I only mine to your pool I have no other pool set in the failover just the solo.ckpool.org only.
Very confused not just me another miner has the same issue.
I don't know how to explain it since that code is truly untouched for years now. Many years ago bitmain had some dodgy firmware that falsely showed block solves when they never happened, but I don't think that persists as an issue. I have no idea what hardware you're using, but are you using braiins firmware or something? That mines for something like 1% of the time at their pool as a fee.