Congratulations to miner bc1q~jr38 for solving the 307th solo block at solo.ckpool.org, with only 200TH!


https://mempool.space/block/0000000000000000000180aab2a364d0baeddacf4048d0600065390a81651829
A miner of this size only has a 1 in ~36,000 chance of solving a block each day, or once every ~100 years!

Congratulations to massive new rental miner bc1q~4kzx for solving the 306th solo block at solo.ckpool.org!


https://mempool.space/block/00000000000000000000978f2aa548b12b9fe7da9e2809d25f2d40ddfb63c1ae

Everything fine as far as I can see. Might be a routing issue from you to the pool.

I highly recommend using a 2:3 multisig. However I don't have the time to be part of one, and obviously some fee to the other parties taking responsibility would be appropriate.

Let me make this clearer: 4334 is ONLY for rentals.

The high port is for rentals, so don't use that.

It's not a bad idea but there's no provision for such a thing in the bitcoin node at present and it would have to be coded up.

No sorry, not under any circumstances. Solo doesn't solve enough blocks anyway for it to make sense.

Sub 1sat/vB transaction discussion and reversal of decision to mine them on solo ckpool.

Block 910440 https://mempool.space/block/00000000000000000000d22167aa0c9d1a49e7878631d6c93ea1b1c87b98ba24 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.


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

All seems fine as far as I can see.

Now bringing http://ausolo.ckpool.org back online. Miners will likely not come back until their DNS updates and ther mining hardware reconnects. I will kick them back from the main pool within an hour to make sure AU miners go back to the correct pool.

The downtime was due to mineracks trying to fix a connectivity quality issue I detected with the pool which unfortunately caused unexpected downtime. Bear with us as we believe to have addressed all remaining issues, and connectivity should be improved as well.

The ausolo pool issue unfortunately appears that it will be responsible for extended downtime, so I am redirecting the AU domain to the main http://solo.ckpool.org and stats once more. mineracks is trying to rectify it as quickly as possible.

Apologies for the inconvenience.

ausolo.ckpool.org is currently down and undergoing unplanned maintenance, sorry about any inconvenience. As always be sure to have a backup pool specified on your miners. We'll try to get it up as soon as possible.

Miner sends small amount of data to pool representing what is required to constitute a low hash from its current stratum template.
Pool submits a submitblock message to bitcoin core with the full block data.
Bitcoin core submits a compact block message describing block header, nonce, transaction IDs, prefilled transactions as needed and extra transactions it thinks may be needed.
The amount of data is variable depending on how much the other node knows, and they may request further data. A full block is only sent to nodes that don't avertise compactblock support.

The ausolo pool had connectivity issues a couple of hours ago, and AU miners were migrated to solo.ckpool.org. If you are on ausolo.ckpool.org and your stats aren't showing up at ausolostats.ckpool.org then you are probably still mining at solo.ckpool.org and your stats will be there. I'll kick miners from solo.ckpool.org by restarting it for miners to go back to their correct pool.

Congratulations to the 2nd solo block solver 35mU~8hK7 in 2 days for solving the 304th solo block at solo.ckpool.org! This was a huge miner with 270PH at the time of solving the block.
https://mempool.space/block/00000000000000000001e6a5aec8788183793b27370ef638b152b4d02f9f0787


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.

Congratulations to miner 35Wu9WPzifv3khCHGeviKVuYo6TQzhyPhF for solving the 303rd solo block at eusolo.ckpool.org with only 49TH!  https://mempool.space/block/000000000000000000012b46e1a7ce322e850afde12422c440ee19d9c1b6d74a


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!

Very nice, but sadly short of a block.

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.