Sub 1sat/vB transaction discussion and reversal of decision to mine them on solo ckpool. Block 910440 is the first block that solo ckpool has mined that has included sub 1sat/vB transactions. I made this change because the bulk of the mining pools are now mining transactions below the default (until now) mempool policy of mining transactions only 1sat/vB or above. The reason for switching solo ckpool was partially out of necessity - if the mempool differs substantially from what other pools are mining, when other pools mine a block with low fee transactions, solo ckpool will be slow to build new blocks. The reason is because of the disparity in what is in the pool's mempool and it missing transactions included, so it would have to ask for the missing transactions before it can build a full block. Now that solo ckpool has mined a block with sub 1sat/vB transactions I have data on the reward mined as the result of a low transaction fee period. Of the ~4900 transactions mined in this block, ~3300 were sub 1sat/vB transactions. It took some time to sift through the data of these transactions to determine what the mined fees were. They amounted to ~.0018 BTC more in fees, or ~$220. This is ~.06% of the current 3.125 BTC block reward. These particular low fee transactions were very small and appeared to create 1-2 UTXOs each. In light of how ridiculously small the extra fees mined were by accepting these transactions, and the potential for creating a significant number of new UTXOs, I am reversing my decision to mine these transactions. To maintain solo ckpool's ability to be aware of these transactions in the mempool I will only be setting the minrelaytxfee to accept and forward them, but not setting a lower blockmintxfee to mine them. The block reward needs to have dropped substantially for such low fee transactions to add meaningful reward to mining pools, and I would only consider doing so if the reward was at least 1% more. The block reward would need to have dropped below 0.2 BTC total meaning we are decades away from such fees to be significant. By that time the landscape is likely to be very different to the current one, and it is unknown if fees will remain low that far away. A lower minimum fee is also likely to worsen fees' ability to be a significant contributor to mining rewards as block subsidy diminishes. I implore other pool owners to do their own calculations and reconsider their decision to mine them at this stage.
Congratulations to miner bc1q~nwsgdw0wfh4trqal69fz with 9PH for solving the 305th solo block at solo.ckpool.org! A miner of this size has about a 1 in 800 chance of solving a block per day. image
Create your own local solo bitcoin mining ckpool & bitcoind easy install It's clear that the default ckpool installation requires a bit of linux knowhow so I've created an all-in-one script to automate the process for you. Quick instructions for most linux distributions: wget https://bitbucket.org/ckolivas/ckpool/raw/master/scripts/install-ckpool-solo.sh chmod +x install-ckpool-solo.sh sudo ./install-ckpool-solo.sh Whilst a dedicated high performance pool for regular or solo mining is still likely the preferred option for most people, everyone should have the ability to run their own truly solo mining operation even if just as their final backup. It should also be easy for as many people as possible to deploy one quickly in the case of an existential mining threat. This will download ckpool source code, v29.0 bitcoin daemon binary, check its validity, install the daemon, build ckpool, and install it, configured for solo mining, and begin downloading the blockchain. Follow the prompts or simply press enter for the default settings. Should work on any .deb or .rpm based linux distribution (ubuntu, debian, fedora, centos, rhel) to download required packages. Installs both as systemd services as the current user but can configure a new ckpool user for both. It will allow you to choose to run a pruned bitcoin blockchain to minimise hard drive storage, but it is recommended to use a full blockchain and have enough storage space to spare. The current blockchain is almost 700GB, so ideally you should at least have double this space on the drive. You will be given the option to use a checkpoint hash to speed up the initial blockchain download, or disable it for maximum paranoia. It will use any existing blockchain data in ~/.bitcoin if it exists for the chosen user. Bitcoind will be preconfigured with suitable mining defaults, and ckpool will be configured to start in solo mining mode on port 3333 on the current machine. You will be unable to mine to it until the bitcoin daemon has synced up the full blockchain. You will be given the option to enable donation to the ckpool author, and a custom signature to be added to any solved blocks. Higher performance modern computing hardware and storage is recommended if you are to maintain a dedicated local solo mine and not just a backup of last resort.
Congratulations to the 2nd solo block solver 35mU~8hK7 in 2 days for solving the 304th solo block at ! This was a huge miner with 270PH at the time of solving the block. A miner of this size has about a 1 in 20 chance of solving a block each day, however this miner doesn't appear to have been mining continuously at that hashrate for very long, and the worker size suggests this was a rental.image
Congratulations to miner 35Wu~yPhF for solving the 303rd solo block at the EU with only 49TH! A miner of this size only has a one in 130,000 chance of solving a block in a year or once every 370 years on average! image
Meanwhile, from Australia's largest airline carrier. Is there anything else that could have been compromised? They may as well have been storing our passwords stored in clear text. FFS. image
Congratulations to miner 35ny~zePa with an enormous 200PH for solving the 302nd solo block solved at ! A miner of this size would solve a block once every ~35 days on average at current mining difficulty.
Saturn captured in above average conditions on 2025-07-08 UTC. image
Announcing ausolo.ckpool.org, another sibling solo ckpool located in Brisbane, Australia to service Oceania/Asia-Pacific miners with low latency solo mining. Just point your miner to: ausolo.ckpool.org port: 3333 This is a standalone pool from solo.ckpool.org and eusolo.ckpool.org for latency and performance reasons, but blocks will be propagated between the sibling pools and you can use each sibling pool as a backup if desired. Blocks mined from ausolo will feature the same solo.ckpool.org signature with a ckpoolau prefix. I fully expect this to be the lowest hashrate solo ckpool consisting mostly of bitaxed sized miners given the electricity prices of Au, but since most of them will be wanting to mine solo, this should fill the gap in the region. There is now solo.ckpool.org coverage with relatively low latency to most parts of the world. The hardware for ausolo has been provided and is being maintained courtesy of mineracks.com Mine on, and good luck!
Saturn captured in infrared 2025-07-08 UTC. image