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

[philipma1957]

somebody hitting a block today. I can feel it in the air.

I could do with some of that 

no me first

[strategiccryptoreserve]

somebody hitting a block today. I can feel it in the air.

I could do with some of that 

no me first

The strategic crypto reserve really needs this lottery bitcoin block please we have so many charities we plan on helping with this block

[ethanhunt2023]

somebody hitting a block today. I can feel it in the air.

I could do with some of that 

no me first

Yes, that's what I've been feeling for the past couple of days. It's almost here.

[Istie]

Can you renew the certificate on https://eusolostats.ckpool.org

Thank you!

[-ck]

Can you renew the certificate on https://eusolostats.ckpool.org

Thank you!

Thanks, should be fixed now.

[eb66]

Mine with Team Rigly on CK Pool, as we try to solo mine a block.

Rigly block party is happening on 2/13 00:00 - 18:00 UTC

- https://blockparty.rigly.io
- Minimum buy-in is just 1,000 sats (21 TH/s)
- Lightning buy-in supported
- Hashpower comes from NiceHash / Mining Rig Rentals
- Bring your bitaxe! bring-your-own-miner is supported

Much respect to Willi's parties, which inspired this effort.

If we see interest, we'll make it a recurring party.

Join us on telegram:
   https://t.me/+K8JjHpTgqoFjZmIx

Mining starts at 00:00 UTC on Friday.

https://blockparty.rigly.io
 

We're back with another block party on Saturday April 25th 00:00 - 18:00 UTC

Much respect to Willi's parties, which inspired this effort.

Mine with Team Rigly on CK Pool, as we try to solo mine a block.

- https://blockparty.rigly.io
- Minimum buy-in is just 1,000 sats (21 TH/s)
- Lightning buy-in supported
- Hashpower comes from NiceHash / Mining Rig Rentals
- Bring your bitaxe! bring-your-own-miner is supported

New! Hashathon during the party

Buy hashrate before the party starts, or join in during the party in the Hashathon.

*** The next 10 buys get a free 21 TH/s boost ***

Join us on telegram:
   https://t.me/+K8JjHpTgqoFjZmIx

https://blockparty.rigly.io

Thanks,

[ethanhunt2023]

It seems like a solo miner mined a block on braiins solo which uses the ckpool software and I wanted to ask you ck if the 2% goes to your btc address which is almost hardcoded in the software?

Block no. 947128.

[ethanhunt2023]

It could be that today is the day of solo mined blocks, and block 947,073 was mined on the public pool..

[-ck]

It seems like a solo miner mined a block on braiins solo which uses the ckpool software and I wanted to ask you ck if the 2% goes to your btc address which is almost hardcoded in the software?

Block no. 947128.

You can see the block for yourself to see how much goes to me.

https://mempool.space/block/0000000000000000000077bd95487d4eac60772e2c762269a465c8d9c59d7f7e

The donation defaults to off in the ckpool code. Braiins have been kind enough to enable 0.5% donation to me still though, since they're using my code.

[ethanhunt2023]

It seems like a solo miner mined a block on braiins solo which uses the ckpool software and I wanted to ask you ck if the 2% goes to your btc address which is almost hardcoded in the software?

Block no. 947128.

You can see the block for yourself to see how much goes to me.

https://mempool.space/block/0000000000000000000077bd95487d4eac60772e2c762269a465c8d9c59d7f7e

The donation defaults to off in the ckpool code. Braiins have been kind enough to enable 0.5% donation to me still though, since they're using my code.

It's good, I'm glad they left 0.5.

IMHO, everyone who uses your code should leave at least 0.5.

[-ck]

Ckpool rework for yyjson. Whilst ckpool is very low overhead and scalable due to being coded in multithreaded C, one of the largest overheads within the code is the json parsing library. Libjansson has been included since 2014 and it touches approximately 5,000 lines of code with ckpool.
Since that time a number of higher performance json libraries have come out, with yyjson proving to be the fastest - 10-100x faster depending on the workload. I've resisted reworking the code for a long time, but the benefits are substantial - not only would ckpool be much lower overhead and even more scalable, it would lead to much faster block template changs which are a critical performance measure in mining pools.
I've embarked upon a major rewrite of all the performance critical components of ckpool to use yyjson. It is unfortunately far from a drop-in replacement and has required some significant surgery. Some of the safer code has already been merged into the master branch on git, but the massive rewrite has been committed to a yyjson branch. I'm currently testing the existing code on testnet4, and will continue refining it further before eventually merging it into the master branch and deploying it on the solo ckpools. The solo ckpool currently would probably safely handle 10x its current load (which is 40,000 clients).
I don't know how much of a real world improvement it will work out to, but I'm hoping for good things. At the very least, faster block changes are always worth pursuing. Watch this space, as I'll be announcing when I'm deploying it on solo.
And no, this isn't a modification any existing AI has a hope in hell of vibe coding, so it's all done by hand. Current code:
https://bitbucket.org/ckolivas/ckpool/src/yyjson/

[chrysophylax]

Ckpool rework for yyjson. Whilst ckpool is very low overhead and scalable due to being coded in multithreaded C, one of the largest overheads within the code is the json parsing library. Libjansson has been included since 2014 and it touches approximately 5,000 lines of code with ckpool.
Since that time a number of higher performance json libraries have come out, with yyjson proving to be the fastest - 10-100x faster depending on the workload. I've resisted reworking the code for a long time, but the benefits are substantial - not only would ckpool be much lower overhead and even more scalable, it would lead to much faster block template changs which are a critical performance measure in mining pools.
I've embarked upon a major rewrite of all the performance critical components of ckpool to use yyjson. It is unfortunately far from a drop-in replacement and has required some significant surgery. Some of the safer code has already been merged into the master branch on git, but the massive rewrite has been committed to a yyjson branch. I'm currently testing the existing code on testnet4, and will continue refining it further before eventually merging it into the master branch and deploying it on the solo ckpools. The solo ckpool currently would probably safely handle 10x its current load (which is 40,000 clients).
I don't know how much of a real world improvement it will work out to, but I'm hoping for good things. At the very least, faster block changes are always worth pursuing. Watch this space, as I'll be announcing when I'm deploying it on solo.
And no, this isn't a modification any existing AI has a hope in hell of vibe coding, so it's all done by hand. Current code:
https://bitbucket.org/ckolivas/ckpool/src/yyjson/

Nice Mate ...

This will be something to behold if it benefits the Pool System.

#crysx #cwi

[Nexus9090]

Ckpool rework for yyjson. Whilst ckpool is very low overhead and scalable due to being coded in multithreaded C, one of the largest overheads within the code is the json parsing library. Libjansson has been included since 2014 and it touches approximately 5,000 lines of code with ckpool.
Since that time a number of higher performance json libraries have come out, with yyjson proving to be the fastest - 10-100x faster depending on the workload. I've resisted reworking the code for a long time, but the benefits are substantial - not only would ckpool be much lower overhead and even more scalable, it would lead to much faster block template changs which are a critical performance measure in mining pools.
I've embarked upon a major rewrite of all the performance critical components of ckpool to use yyjson. It is unfortunately far from a drop-in replacement and has required some significant surgery. Some of the safer code has already been merged into the master branch on git, but the massive rewrite has been committed to a yyjson branch. I'm currently testing the existing code on testnet4, and will continue refining it further before eventually merging it into the master branch and deploying it on the solo ckpools. The solo ckpool currently would probably safely handle 10x its current load (which is 40,000 clients).
I don't know how much of a real world improvement it will work out to, but I'm hoping for good things. At the very least, faster block changes are always worth pursuing. Watch this space, as I'll be announcing when I'm deploying it on solo.
And no, this isn't a modification any existing AI has a hope in hell of vibe coding, so it's all done by hand. Current code:
https://bitbucket.org/ckolivas/ckpool/src/yyjson/

Thanks for the update -CK

Doing the job properly is the best solution. I can't understand why anyone would risk using an AI tool to "vibe" code critical software, its asking for trouble!

Do you intend to deploy a testnet4 pool for public testing prior to pushing to ckpool on mainnet, I'd happily point a bitaxe or two at it, if it would help with testing.

Anyway, take your time and best of luck getting it all coded in and tested.

[-ck]

Thanks for the update -CK

Doing the job properly is the best solution. I can't understand why anyone would risk using an AI tool to "vibe" code critical software, its asking for trouble!

Do you intend to deploy a testnet4 pool for public testing prior to pushing to ckpool on mainnet, I'd happily point a bitaxe or two at it, if it would help with testing.

Anyway, take your time and best of luck getting it all coded in and tested.

Thanks for that. Canaan have kindly donated some hardware so I can point it at testnet4 locally with about 100TH.  I've already solved 2 blocks during testing, but it takes ~12 hours on average.

[Nexus9090]

Thanks for the update -CK

Doing the job properly is the best solution. I can't understand why anyone would risk using an AI tool to "vibe" code critical software, its asking for trouble!

Do you intend to deploy a testnet4 pool for public testing prior to pushing to ckpool on mainnet, I'd happily point a bitaxe or two at it, if it would help with testing.

Anyway, take your time and best of luck getting it all coded in and tested.

Thanks for that. Canaan have kindly donated some hardware so I can point it at testnet4 locally with about 100TH.  I've already solved 2 blocks during testing, but it takes ~12 hours on average.

You're welcome, I'm expect many of us would be happy to point some hashing power to a test node if it will help prove the changes before mainnet deployment.

Anyway, keep us posted

Thanks!

[-ck]

Anyway, keep us posted

For sure.  I've successfully replaced all the performance critical json in the main pool code and the bitcoin daemon parsing, leaving other modes (proxy, passthrough, node, etc.) to use the old code, and have addressed all the potential memory leaks. The code's looking very solid right now and I'm hoping to get it up in a day or two on solo. I'll deploy it in a staggered timeframe over the 3 pools as each proves stable.

[ethanhunt2023]

Anyway, keep us posted

For sure.  I've successfully replaced all the performance critical json in the main pool code and the bitcoin daemon parsing, leaving other modes (proxy, passthrough, node, etc.) to use the old code, and have addressed all the potential memory leaks. The code's looking very solid right now and I'm hoping to get it up in a day or two on solo. I'll deploy it in a staggered timeframe over the 3 pools as each proves stable.

Very good, and thank you for the work you do for the community.

[-ck]

I'm deploying this modified code on solo.ckpool.org in a couple of hours. Hopefully this should be completely transparent to miners who won't notice anything, but as always make sure to have a backup pool configured in case of unexpected downtime.

[-ck]

I'm deploying this modified code on solo.ckpool.org in a couple of hours. Hopefully this should be completely transparent to miners who won't notice anything, but as always make sure to have a backup pool configured in case of unexpected downtime.

The yyjson performance upgrade has been deployed on https://solo.ckpool.org and it's running smoothly, but I'll be monitoring it carefully for any instability. It is too early to gauge the performance improvement, but it already appears to be using less CPU on average. The most important change is block changes will occur 30-50ms faster. Once stability is confirmed for 24 hours I will switch the other two pools to the new code, and merge it into the git master branch.

Mine on!

[-ck]

So far only minor cosmetic issues have come up on the logs, and I've done a few seamless restarts to address them, meaning things are still looking good. On the upside, the average CPU load is levelling out to about 2/3 of what it normally is overall, which is a huge performance increase at any time, let alone for otherwise mature software. It equates to 50% more capacity for the pool. This confirms it was well worth the effort. I'll continue to closely monitor its behaviour. The other two pools will be upgraded only once no more issues - cosmetic or otherwise - show up. A block right now would be the icing on the cake.
Mine on!