Stratum Protocol Comparison for Solo Miners
Stratum protocol comparison for Bitcoin miners: Stratum V1 and V2 differ in encryption, job control, and what your rig can actually use today.
A Stratum protocol comparison matters only after the connection works. Your miner needs a valid Bitcoin payout address, a pool endpoint, and a protocol its firmware can speak. The rest is a question of what crosses that connection, who can read it, and what the pool can show when a share or block is found.
For most home miners, Stratum V1 remains the practical answer. Bitaxe-class hardware and many standard ASICs speak it already. Stratum V2 changes useful parts of the transport and message format, but support in small open-source miners is still limited. A protocol setting cannot create luck. Network difficulty sets the odds at every pool. Solo mining is a lottery, and an average wait is not a schedule.
NexusPool (nexuspool.io) accepts Stratum V1 and encrypted Stratum V2 on the same Bitcoin address and port: solo.nexuspool.io:3350. That lets a miner use its current firmware without selecting a different pool path just because the firmware lacks V2.
Stratum V1: the protocol most rigs already use
Stratum V1 is the long-standing mining connection used by a large share of Bitcoin mining hardware. It is text-based. A rig subscribes, authorizes with its configured credentials, receives jobs, and submits shares. The messages are readable JSON lines, which makes the protocol relatively easy for firmware authors and operators to inspect.
That readability has a cost. Classic V1 does not encrypt the connection by itself. A party that can observe or alter traffic between a rig and the pool may be able to see job messages or interfere with them. What that means in practice depends on the miner's network, the route to the pool, and whether the local network is trusted. It is not a reason to pretend every home connection is under attack. It is a reason to describe the boundary accurately.
V1 also leaves more room for implementation differences. A rig may format a submit one way. A pool may parse only the fields it expects. When those interpretations differ, a miner sees rejected shares and often gets little useful detail.
At NexusPool, the pool reads a V1 share in the form the firmware sent. It returns a reason for shares it reads and rejects. This does not turn an invalid share into a valid one. It gives the operator a place to start: stale work, an incorrect nonce field, a duplicate, a low-difficulty share, or another stated cause.
What V1 does well
V1 has broad hardware support. A home miner can usually enter a Bitcoin address in the username field, save the pool configuration, and begin receiving work. That matters more than a protocol feature a device cannot use.
V1 can also support version rolling, where the pool grants a miner permission to change selected bits in the block version field. The rig can search additional header space without waiting for a wholly new job. This is a V1 feature with limits defined by the pool's mask and the miner's firmware. It is not a new source of hashes, and it does not change the network target.
The weakness is that V1 was designed before encrypted mining connections were a normal expectation. Its text framing also carries more overhead than a compact binary protocol. That overhead usually matters more at larger scale or on constrained connections than it does to one low-hashrate home rig.
Stratum V2: encrypted transport and tighter messages
Stratum V2 replaces the line-oriented V1 message style with binary messages. It uses Noise encryption for the connection. Encryption prevents passive observers on the path from simply reading the mining messages, and authentication gives the miner a way to check which authority it connected to when its firmware supports key pinning.
The protocol separates responsibilities more clearly. It defines channels for mining work, has explicit message types, and avoids much of the ambiguous text parsing that V1 implementations accumulated over time. These are engineering benefits, not a promise that every V2 connection behaves identically. The pool and firmware still have to implement the same parts of the specification correctly.
A V2 rig can pin a published authority key. The rig then checks the server identity during its encrypted handshake instead of accepting any endpoint that answers in the expected format. All four NexusPool Bitcoin regions sign Stratum V2 with one published authority key. A pinned miner should still be tested through the region and failover behavior it will actually use. Key pinning does not by itself prove that a pin will survive every regional failure case.
V2 also has a feature that gets overstated: job negotiation. In the right arrangement, it can separate template construction from the pool connection and give miners a role in selecting transactions. That requires support beyond merely turning on V2. A V2 transport connection does not mean a home miner is building its own block templates. Ask what job mode a pool and firmware actually run before treating job negotiation as active.
What V2 changes for a home miner
If your miner supports encrypted Stratum V2, use it when you can verify the authority key and understand the firmware setting. You gain encrypted mining traffic and a more structured protocol. You do not gain a different probability of finding a block.
If your miner supports only V1, keep the comparison in proportion. V1 support is not a defect in a miner that otherwise runs correctly. The useful questions are whether it receives new work promptly, whether rejected shares have stated reasons, and whether a valid found block has a documented submission path.
For a Bitaxe, NerdQaxe++, NerdOCTaxe, Avalon Nano 3S, or a standard V1 ASIC, the connection path comes first. Enter your Bitcoin address as the configured worker identity, use solo.nexuspool.io:3350, and select the protocol your firmware supports. Do not add an account name that the pool does not require.
The comparison that affects a found block
Protocol choice is only one part of the path from a hash to a block. A miner needs current work. It needs its submission interpreted correctly. If it finds a valid block, the pool must construct and send that block before another block makes it stale.
On Bitcoin, NexusPool prepares work when it receives a new block header, before its node finishes validating that block. On the Frankfurt server, the median time from header receipt to work was 0.49 ms across 162 mainnet blocks on September 10 and 11, 2026. That work was 205 ms ahead of validation. The first job carries no transactions because validation is not complete. That is a stated trade-off: earlier work, then a complete transaction-bearing job after the node can safely provide it.
A block found through Los Angeles, Chicago, or Frankfurt goes to disk first and then to Bitcoin nodes in all three cities. The pool retries each submission for up to five minutes. Singapore sends a found block to its own node. After a restart, the pool submits a pending block again. These mechanics apply after the rig has done the rare part: produced a block-valid hash.
Neither V1 nor V2 makes that hash more likely. A shorter route may reduce how long a rig works on an old block after the network changes. A longer route can delay jobs and statistics for miners far from the available regions. Distance does not alter the odds set by hashrate and network difficulty.
Pick the protocol your rig can verify
Choose V2 when your firmware supports it, you can configure the published authority key, and you want encrypted mining traffic. Choose V1 when that is what your hardware speaks. Do not replace working firmware solely to obtain a label.
Then check the part that matters if the lottery ticket wins. Before you mine, use Payout Preflight to inspect the payout built for your Bitcoin address on the current block. The expected subsidy and transaction fees are shown in the block payout output before your rig finds anything. If the rig finds the block, the whole reward goes to that address inside the block. There is no balance held for later withdrawal.
Trust nothing. Verify the payout output before you point a rig at solo.nexuspool.io:3350.