Stratum V1

Stratum V1 is the original pooled-mining protocol that has connected ASIC hardware to mining pools since 2012. It runs line-delimited JSON-RPC over a plain TCP socket: human-readable text messages, one per line, in each direction. Its simplicity made it trivial to implement and drove near-universal adoption — virtually every miner ever sold speaks it — but the same design carries real limitations that its successor exists to fix.

The protocol lifecycle

A session follows a fixed choreography. The miner may open with mining.configure to negotiate extensions, then sends mining.subscribe to register for work — the pool answers with extranonce1, a session-unique value, and extranonce2_size, the number of bytes the miner may vary on its own. After mining.authorize identifies the worker, the pool pushes jobs with mining.notify and tunes share rate with mining.set_difficulty. To generate unique work, the miner splices its extranonce into the coinbase transaction between the pool-supplied halves, rebuilds the merkle root, and grinds nonces; matching results go back via mining.submit. A clean_jobs flag on new work tells the miner to abandon stale jobs immediately — the signal that a new block was found.

Known weaknesses

Three flaws matter most. First, the traffic is unencrypted plaintext, exposed to man-in-the-middle attacks in which an intermediary silently redirects a victim's hashrate to a different pool — a real-world theft vector on unsecured networks, since nothing in the protocol authenticates the pool to the miner. Second, the verbose JSON encoding wastes bandwidth at fleet scale compared to a binary framing. Third — and most important structurally — the pool alone constructs every block template, so individual miners have no say over which transactions their hardware confirms. Transaction selection for most of the network's hashrate concentrates in a handful of pool operators, a standing centralization pressure on Bitcoin itself.

Extensions and successor

Some gaps were patched through negotiated extensions — most notably version rolling, defined in BIP 310, which lets miners vary bits of the block-header version field to gain extra nonce space for overt ASICBoost; modern hardware depends on it. But the deeper issues — encryption, efficiency, and decentralized template selection — are addressed only by Stratum V2, which adds an encrypted binary transport and, through its Job Declaration and Template Distribution sub-protocols, lets miners build their own blocks. Native V2 support in firmware remains the exception rather than the rule, so V1 is still what the overwhelming majority of deployed hardware actually speaks, with translation proxies bridging old machines onto new infrastructure.

On the workbench

For the home miner, V1's readable JSON is genuinely useful: you can watch a session with a packet capture and diagnose pool trouble by eye — wrong worker name, rejected shares, difficulty swings — with no special tooling. Every stock firmware dashboard's pool settings map straight onto the handshake described above, so understanding the message flow is understanding your miner's most important conversation.

Native Stratum V2 support illustrates how slowly mining infrastructure actually turns over: years after the successor's specification stabilized, only a minority of firmware speaks it natively, and the bulk of the world's hashrate still opens a plain V1 TCP socket every time a machine boots. That inertia is not laziness — it is the natural consequence of a protocol that was simple enough to implement everywhere, from industrial fleet controllers down to a Bitaxe on a desk. Understanding V1 therefore remains mandatory knowledge even for miners who intend to leave it behind; it is the lingua franca every pool, proxy, and dashboard still speaks.

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