CKPool Turned On Stratum V2 for Solo Miners. Here's How to Check Your Own Connection

CKPool, one of the best known solo Bitcoin mining pools, activated Stratum V2 on its solo servers in August 2026. Stratum V1 keeps working unchanged, so nobody's rig went offline, but every miner pointed at CKPool now has the option to run an encrypted connection instead of a plain-text one. CKPool also turned on job declaration, the feature that lets a miner build their own block template, though the pool's own operator has cautioned it adds latency and is not yet recommended for solo mining specifically.

If you run a Bitaxe, a NerdQAxe, or any other open-hardware solo rig, this is a good excuse to actually check what protocol your miner is speaking today, rather than assuming. Here is how to do that, step by step, on whatever pool you use.

Step 1: Understand what Stratum V2 encryption actually buys you

Stratum V1 sends your mining traffic, including your share submissions and your payout address, in plain text. Anyone positioned between your miner and the pool, a compromised router, a malicious ISP, a hostile network operator, can read it or tamper with it. Stratum V2 wraps that traffic in the Noise protocol, an encryption handshake pinned to the pool's authority key, so your rig only trusts the pool it's actually configured to trust. It does not change your odds of finding a block. It changes whether someone snooping your home network can see or interfere with your mining traffic while you try.

Step 2: Check which protocol your rig is using right now

Most solo-mining firmware exposes this in its own dashboard. AxeOS (the firmware behind Bitaxe and NerdQAxe devices) shows the active stratum URL and port in its web interface; a V1 connection typically uses a plain stratum+tcp:// URL, while a V2 connection needs a V2-capable endpoint and, in most current implementations, a distinct port or proxy. If your configuration screen just shows a hostname and port you copied from a guide two years ago, you are almost certainly still on V1. That is not dangerous by itself, but it means you have not made a choice, someone else made it for you by default.

Step 3: Test the encrypted connection without breaking your current setup

Do not overwrite your working configuration in place. Most rigs let you save a second pool profile, so add the pool's V2 endpoint as a backup entry rather than replacing your primary one. Point it at the V2 port if the pool exposes native V2, or through a translation proxy if it does not (a proxy speaks encrypted V2 upstream to the pool and plain V1 downstream to your miner, so nothing in between your router and the proxy needs to trust anyone). Watch your device's accepted-share count for ten or fifteen minutes after switching. If shares keep accruing normally, the connection is working.

Step 4: Decide whether job declaration is worth enabling yet

Job declaration, the part of Stratum V2 that lets your own node choose which transactions go in a block template instead of the pool choosing for you, is the most meaningful decentralization piece of the protocol. It is also the newest and least battle-tested for solo mining specifically, per the pool's own operator guidance mentioned above. Unless you are comfortable running your own full node and troubleshooting the extra latency it introduces, it is reasonable to enable encryption first and leave template construction for later. Nothing about that choice affects whether a block you find pays you.

Step 5: Confirm the payout address hasn't moved

This is the step people skip. After any pool or protocol change, reload your miner's settings page and read the payout address back character by character, or at minimum compare the first and last six characters against your own records. A copy-paste error into the wrong field, or a stale saved profile pointing at an old address, is a far more common way to lose a solo mining payout than any protocol-level attack. NexusPool's Payout Preflight tool exists for exactly this reason: it reconstructs a coinbase transaction against your configured address before a block is even found, so a misconfiguration shows up on a dry run instead of the one time it would actually matter.

NexusPool runs native Stratum V1 and Stratum V2 with the same-port protocol auto-detection described on NexusPool's technology page, so older and newer firmware both connect without a manual switch, and any configuration changes you make are logged on NexusPool's changelog. That is a design choice, not a claim that any particular pool's implementation is better or worse than another's; the public Stratum V2 specification is the actual authority on what the protocol does and does not guarantee.

None of this changes your odds of finding a block. Odds are set entirely by your hashrate divided by the network's current hashrate, the same for every miner on a chain regardless of which pool, protocol, or hardware they use, and nothing here is investment advice or a promise of any return.

To recap: know what protocol you're actually running, test a new connection on a second profile before trusting it, treat job declaration as optional for now, and always re-read your payout address after any change. If you only do one of these, do the last one.

Trust nothing. Verify your own stratum connection.