Stratum V2

Definition: Stratum V2 (Sv2) is an open protocol specification for communication among Bitcoin mining devices, pools, and related services. It defines how mining work and shares can be exchanged, with optional mechanisms that let miners select or declare transaction sets when compatible pool and template-provider software supports them. It does not change Bitcoin consensus rules or make every pool support miner-selected block templates.12

Full nameStratum V2
CategoryBitcoin mining communication protocol
Main purposeStandardize mining-job and share communication between compatible clients and servers1
Optional transaction selectionJob Declaration can support miner-selected work when the pool, client, and template provider are configured for it2
DirectoryBitcoin Directory

What Stratum V2 does

Mining software needs to receive work, send proof-of-work shares, and report a valid block solution. Stratum V2 specifies these messages and organizes communication into channels so a client and server can manage mining work over a connection. The specification uses a binary message format and defines protocol behavior more precisely than the historically varied Stratum V1 implementations. Its design goals include reducing redundant traffic and computation while preserving fast share reporting for pool accounting.1

That scope matters: Sv2 is a communication layer used by mining equipment and services. It does not set Bitcoin’s block interval, difficulty adjustment, subsidy, or consensus rules. A pool can change its mining communication software without changing Bitcoin itself, and miners still need compatible firmware, proxies, or other integration software to connect.

Job Declaration and transaction choice

Stratum V2’s Job Declaration Protocol is the feature most often associated with miner choice over block contents. In a compatible setup, a Job Declarator Client can receive a block template from a Template Provider and declare custom mining work to a Job Declarator Server associated with a pool. The pool can accept or reject the declared work. Depending on the configured mode, the pool may see only information needed to assess the coinbase, or the Job Declarator Server may validate a fuller transaction template. The protocol also defines fallback behavior so a client can change pool or, as a last resort, mine solo if required acknowledgements do not arrive.2

ComponentRolePractical limit
Mining ProtocolMoves jobs, channel updates, shares, and solutions between mining clients and servers.Both sides need compatible software and configuration.
Template DistributionProvides block templates and transaction data to a client or other mining component.Miner choice depends on having a usable template source.
Job DeclarationLets a client declare custom work to a pool-side server for review.A pool can decline; the feature is optional and requires the relevant components.
Translator or proxyCan bridge parts of a deployment that still use older miner firmware.Compatibility and supported functions depend on the particular implementation.

Job Declaration is therefore a capability, not a guarantee that every connected miner controls the transactions in a block. It requires compatible pool infrastructure and a source of templates, and the pool can reject custom work. Claims about decentralizing transaction selection should be read as a potential effect of deployment and adoption, not an automatic result of the protocol alone.2

Encryption and connection security

The specification describes authenticated encryption to protect message confidentiality and integrity. It also describes a Noise-based key-agreement handshake for establishing secure sessions. The security document says that this handshake is optional on a local network, such as between a miner and local proxy, and mandatory for remote connections to upstream services such as pools, Job Declarator servers, and template distributors. Actual protection still depends on the implementation and its configuration; the protocol specification is not a security audit of a pool or mining device.3

Adoption and limitations

Using Stratum V2 requires support across the relevant parts of a mining setup: pool software, miner firmware or a translator, and sometimes template-distribution and job-declaration services. A miner cannot obtain transaction selection merely by connecting to a pool that supports ordinary share submission. Operators should check the exact protocol features supported by their pool, device, proxy, and software versions before changing a production configuration. Public reference implementations and specifications help developers build compatible systems, but they do not establish how widely a feature is deployed across the network.1

History

  • October 2022: The Stratum V2 Reference Implementation reported an update that let miners using Stratum V1 firmware connect to an Sv2-compatible pool.4
  • 2023: The working group renamed “Job Negotiator” to “Job Declarator” to clarify that miners declare custom work for a pool to accept or reject.4
  • August 3, 2023: The project published a roadmap describing specification updates and two implementation paths: Braiins’ implementation and the Stratum V2 Reference Implementation. This is a dated project snapshot, not a current adoption count.4

Page updated: November 10, 2026.

Related Terms

Related Articles

See Also

Sources

  1. Stratum V2 Working Group. “Stratum V2 Protocol Specification.” Accessed November 10, 2026. Specification repository.
  2. Stratum V2. “Job Declaration Protocol.” Accessed November 10, 2026. Protocol documentation.
  3. Stratum V2 Working Group. “Protocol Security.” Accessed November 10, 2026. Security specification.
  4. Stratum V2. “Stratum V2 (SRI) Roadmap—To Infinity and Beyond.” August 3, 2023. Roadmap and implementation history.