Stratum V2 update on solo.ckpool.org. I've tried to minimise posting since the coldcard exploit was discovered to not affect signal to noise ratio on that issue.
It's been about a week since SV2 was deployed across all solo ckpool endpoints. SV2 has peacefully coexisted with the existing stratum V1 endpoints and no regressions have been noted. Take up has been modest with ~120 users mining SV2, heavily biased towards the EU and SG servers.
A block was solved on the pool in that period without any issues on stratum V1, confirming functionality was completely unaffected.
All the SV2 code has been merged into the master branch of ckpool as run on the pool itself
https://bitbucket.org/ckolivas/ckpool/src/master/ . Some minor bugs were addressed in the code in addition to the SV2 implementation.
The ckproxy code has been updated to support upstream SV2 pools as well (including pools that support Job Declaration, if you set up a local bitcoin node with it.) If you were looking to try mining SV2 without any SV2 compatible hardware, ckproxy can act as the gateway for all your hardware.
"Red team" recently performed a security audit on the ckpool code and possible security holes were all addressed. Thanks goes to @Rob1Ham , @callebtc , @PortlandHODL and their team for their tireless efforts. These were deployed across all the pools without discernible downtime to miners.
As a reminder there is no burning need for miners to switch to SV2. What it offers is more privacy, security, and minor bandwidth improvements - it doesn't affect performance, hashrate, rejects etc.
In other solo ckpool news, a higher performance server was seamlessly deployed for West USA, and stratum.ckpool.org now also will redirect to IPv6 endpoints when available.