Stratum V2 Setup — Connect Your Miner

This is the configuration reference for connecting a Stratum V2 miner to SoloFury. Everything you need is on this page: endpoints, ports, the authority public key, and the exact fields for each firmware. For what the protocol actually does and why it matters, see our complete Stratum V2 guide — this page assumes you already decided to use it and just want it working.

What you need before starting

Stock firmware does not work. No Antminer ships with a working Stratum V2 client — not the S21, not the S23. Stock WhatsMiner, VNish, LuxOS and Canaan firmware are all V1-only. If you are on any of those, either flash Braiins OS+ or stay on V1, which SoloFury serves on the same hosts. The protocol comparison explains why this misconception spread.

Connection settings

V1 and V2 share the same ports. The pool detects which protocol your miner speaks and answers accordingly, so a mixed fleet of V1 and V2 machines can point at a single address with nothing to reconfigure.

Endpoints — pick your nearest region

Latency matters more in V2 than people expect: faster job delivery means fewer stale shares, which is where part of V2’s efficiency gain actually comes from.

Not sure which is closest? The Start wizard measures latency from your connection and picks for you, then generates the exact strings for your firmware.

The authority public key — do not skip it

That long base58 string is what lets your miner verify, cryptographically, that the endpoint answering on port 3333 is really SoloFury and not someone who intercepted your DNS or your route. It is the same trust model as an SSH host key.

9cLif4sCxvAz7FBP7GPvYG8Mv586ZhdgNbn3f4PsrM56gboSZEp

Without it your miner connects to whoever answers. With it, an impostor fails the handshake and your hashrate never leaves the building — which is what closes hashrate hijacking as a category of attack.

The key is identical across all nine regions. One value, every endpoint. It is public by design — publishing it is what makes verification possible.

Setup by firmware

AxeOS — Bitaxe

Open the miner’s web interface and go to Settings → Pool Configurations. AxeOS 2.14 and later give you individual fields rather than a single URL:

Stratum Host          eu-btc.solofury.com
Stratum Port          3333
Stratum Protocol      Stratum V2
User                  bc1qYourAddress.bitaxe
Password              x
SV2 Channel Type      Extended
SV2 Authority Pubkey  9cLif4sCxvAz7FBP7GPvYG8Mv586ZhdgNbn3f4PsrM56gboSZEp
Decode Coinbase Tx    enabled

Channel type: Extended sends you the coinbase template so the miner can verify it; Standard has the pool precompute more and sends only the header, which is lighter on an ESP32. Extended is what makes coinbase verification possible — start there.

Decode Coinbase Tx turns that data into something readable on the miner’s screen. Leave it on; it is the single most useful thing V2 gives a solo miner.

Set a second pool as fallback on the V1 port (6060) while you are in there. If anything about V2 misbehaves, the miner keeps hashing instead of sitting idle. New to Bitaxe? Start with the Bitaxe solo mining guide.

NerdQAxe firmware

The Nerd-series firmware shares its V2 implementation with AxeOS — same developer, same fields, same behaviour. Open the web interface, go to Settings → Pool, select Stratum V2, and enter the same host, port, user, password and authority public key as above.

Firmware 1.0.37 or later is required. Covers NerdAxe, NerdQAxe+, NerdQAxe++ and NerdOCTAxe.

Braiins OS+ — Antminer

Braiins takes a different approach: instead of a separate field, the authority public key goes in the URL path. This is the single most common setup mistake, because a URL that looks correct fails silently without it.

stratum2+tcp://eu-btc.solofury.com:3333/9cLif4sCxvAz7FBP7GPvYG8Mv586ZhdgNbn3f4PsrM56gboSZEp

Go to Configuration → Pool Groups, set the protocol selector to Stratum V2, paste that URL, set the worker to address.workername, and save.

Use port 3343 for S21-class machines so the pool starts them at a difficulty matched to their hashrate. Install Braiins OS+ 26.07 or later — versions before 26.05.1 carry a known S21+ underperformance bug in warm conditions, and older builds use a deprecated form of one V2 channel message. See also the Antminer S21 setup guide.

Verify you are actually on V2

This section exists because of a specific failure mode: a V2 config that silently falls back to V1 produces no error. The miner connects, shares are accepted, the dashboard looks healthy — and you are on the protocol you were trying to leave. Three independent checks close that gap.

1. Ask your firmware

Every V2-capable firmware reports the negotiated protocol in its pool status. AxeOS shows Mode: SV2 Extended Channel or similar on the info screen; Braiins OS+ shows the protocol version in pool status. If it says V1 after you configured V2, the config did not take.

2. Check the PROTOCOL column

Open your miner page with your address and look at the worker table. Each worker carries a PROTOCOL badge — grey for SV1, orange for SV2. It reflects how that specific session connected, so a mixed fleet shows both, worker by worker.

The same field is available programmatically: /api-btc/client/{address} returns protocol, availableIn and channelCount per worker. See the API documentation.

3. Read the coinbase from your own hardware

With an Extended channel and coinbase decoding on, the miner receives the actual coinbase transaction template and displays its outputs:

Block Header
  Height       963788
  Scriptsig    SoloFury
  Value        3.14278556 BTC

Outputs
  bc1q68eg...vyd2ey      0.03142785 BTC     (1%)
  bc1qavkk...n0tlw9      3.11135771 BTC     (99%)

Your miner — not the pool’s dashboard, not a block explorer — is showing you that if this block is found, 99% of the reward is addressed to your wallet. Before a single hash is spent on it. That is the strongest guarantee in solo mining, and almost nobody uses it.

Troubleshooting

Why BTC only

SoloFury’s V2 stack talks to the node through Bitcoin Core’s IPC mining interface — a Cap’n Proto socket that hands block templates to the pool the moment mempool fees move. No other SHA-256 chain implementation currently exposes an equivalent: not Bitcoin Cash Node, not Bitcoin ABC, not the BC2 or BCH2 daemons.

Until they do, BCH, BC2, BCH2 and XEC stay on Stratum V1 with full version-rolling and AsicBoost support on their existing ports. That matters for hardware choice: a Bitaxe pointed at BTC over V2 gets encryption and verification, while the same Bitaxe pointed at BCH2 for better block odds runs V1. Both are legitimate — see solo mining vs pool mining and our coin selection analysis for the trade-off.

Going deeper