Stratum V2

Stratum V2 (SV2) is a ground-up redesign of the protocol that connects mining hardware to pools. Where the original Stratum sends unencrypted JSON-RPC text, SV2 uses a compact binary message format wrapped in mandatory encryption — a Noise-protocol handshake (the Noise_NX pattern over secp256k1) establishing ChaCha20-Poly1305 encrypted frames. The result is lower bandwidth, faster share submission, and protection against the hashrate hijacking and man-in-the-middle attacks that plaintext mining traffic invites: on Stratum V1, anyone positioned on the network path can silently redirect your hashrate to their own account, and SV2's authenticated encryption closes that hole outright.

A modular family of sub-protocols

SV2 is not a single channel but a family of sub-protocols that operators can adopt piecemeal. The Mining Protocol is the core, carrying jobs and shares between hardware and pool — deployable on its own as a drop-in upgrade that delivers the efficiency and security wins without changing who builds blocks. The optional Job Declaration Protocol lets a miner construct and declare its own block template to the pool, and the Template Distribution Protocol feeds that template from the miner's own local Bitcoin node. Channels come in standard and extended flavors, so everything from a USB-class device to a proxy aggregating a warehouse can speak the same protocol efficiently. Header-only mining, meanwhile, slashes the data each device must process per job — the machine works on an 80-byte block header rather than shuffling full transaction sets.

Why it matters for decentralization

Under V1, the pool alone decides which transactions enter every block its miners produce, concentrating block-construction power — and with it, censorship capability — in a handful of pool operators. SV2's declaration path returns transaction selection to the individual miner: your node, your mempool, your template, with the pool still coordinating payouts. Distributed across thousands of independent operators, that choice becomes very hard for anyone to pressure. This is the same decentralization argument that drives solo mining, but without giving up pooled payout variance smoothing — a genuine structural improvement rather than a trade-off.

Adoption status

Support has grown from one implementation to several fronts. Natively, Braiins OS+ carries SV2 on industrial Antminers, and the open-source AxeOS/ESP-Miner firmware added native SV2 for Bitaxe-class devices in v2.14.0 (June 2026) — a meaningful milestone, because it puts the most decentralization-forward protocol on the most decentralization-forward hardware. Other major aftermarket firmwares remain V1-only today. For everything else, the open-source Stratum Reference Implementation (SRI) provides a translation proxy: stock-firmware machines speak V1 to a local proxy, which speaks encrypted SV2 upstream — a practical migration path that requires no firmware change at all. Pool-side support exists but is still the minority, so check your pool's documentation before planning a deployment.

On the bench

For a home operator, the practical wins are concrete: encrypted traffic means your ISP or anyone on your LAN path cannot fingerprint or hijack your mining, binary framing helps on thin uplinks, and pairing the job-declaration path with the Bitcoin node you already run makes your hashrate censorship-resistant end to end. When troubleshooting connections, remember the transport is fundamentally different — you cannot debug SV2 with the plaintext tricks that work on V1; see the error-code reference below for both protocols.

SV2 is best understood as Bitcoin applying its own values to its own plumbing: encrypt the wire, verify the counterparty, and push decision-making to the edges. Adoption has been slower than the design deserves, but every firmware release and pool integration moves block construction a little further out of a handful of hands — which is the whole point.

Full open-data reference: Stratum Error-Code Reference — CSV / JSON + REST API, CC BY 4.0.