TL;DR: What Is Stratum V2?
Stratum V2 is the next-generation Bitcoin mining protocol that replaces the decade-old Stratum V1. It encrypts all miner-pool communication, reduces bandwidth by up to 70%, and introduces job negotiation — letting miners choose which transactions go into their block templates instead of blindly accepting whatever the pool dictates.
What Is Stratum V2?
Every Bitcoin miner in the world communicates with its mining pool through a protocol called Stratum. The original Stratum protocol (now called V1) was created by Marek “Slush” Palatinus in 2012 as a quick, practical solution for pooled mining. It worked. It worked so well that for over a decade, virtually the entire Bitcoin network ran on it — unencrypted JSON messages flying between miners and pools in plaintext, with pools holding absolute authority over what goes into every block.
Stratum V2 is the complete rewrite. Developed by Braiins (the company behind the original Slush Pool) and now maintained as an open-source project by the Stratum V2 Reference Implementation (SRI) working group, it addresses every significant limitation of V1: no encryption, no miner-side transaction selection, bandwidth waste, and vulnerability to man-in-the-middle attacks.
If Stratum V1 was a miner obediently executing orders from a central command, Stratum V2 is a miner that encrypts its communication channel, verifies the identity of the pool, and — if it chooses — constructs its own work orders. It is the protocol upgrade that brings Bitcoin mining closer to what Satoshi described in the whitepaper: individual nodes independently validating and constructing blocks.
For home miners, this is not abstract. It means your ISP cannot see that you are mining Bitcoin. It means a hostile actor on your network cannot redirect your hashrate to a different pool. And it means you can run a Bitcoin full node and actually use it to decide which transactions your miner includes in block templates — exercising genuine sovereignty over your contribution to the Bitcoin network.
Stratum V1 vs. Stratum V2: Full Technical Comparison
The differences between V1 and V2 are not incremental tweaks. They are fundamental architectural changes.
| Feature | Stratum V1 | Stratum V2 |
|---|---|---|
| Data Format | JSON (text-based) | Binary (compact) |
| Encryption | None — plaintext | AEAD encryption (end-to-end) |
| Authentication | None | Public key-based certificate authority |
| Man-in-the-Middle Protection | Vulnerable | Protected (verified endpoints) |
| Bandwidth Usage | High (verbose JSON) | ~60-70% reduction |
| Block Template Source | Pool only | Pool or miner (job negotiation) |
| Job Negotiation | Not supported | Supported (optional) |
| Block Propagation Latency | ~325 ms (average) | ~1.4 ms |
| Empty Block Mining | Common (due to template delay) | Virtually eliminated |
| Forward Secrecy | No | Yes |
| Connection Multiplexing | One connection per device | Multiple logical channels per connection |
| Proxy Support | Basic | Native translation proxy (V1 devices connect through V2 proxy) |
The headline numbers are dramatic. Block-switching latency drops from 325 milliseconds to 1.42 milliseconds — a 229x improvement. This alone saves approximately 4.9 hours of wasted hash power per year for the average mining operation. When you are competing for block rewards worth $300,000+, those recovered hashes translate directly to revenue. Braiins estimates the combined efficiency gains can boost net mining profits by up to 7.4%.
Why Stratum V2 Matters for Decentralization
This is the section that matters most. Everything else — the encryption, the bandwidth savings, the speed improvements — is engineering polish. Job negotiation is the revolution.
Job Negotiation: Miners Choose Transactions
Under Stratum V1, the pool constructs the block template. The pool decides which transactions to include, in what order, and which to exclude. The miner receives this template and blindly hashes against it. The miner has zero say in the content of the block it is working to produce.
This means that in early 2026, a handful of pool operators — Foundry USA, AntPool, F2Pool, SpiderPool — decide the contents of roughly 70% of all Bitcoin blocks. If these operators wanted to censor a specific transaction, exclude a specific address, or implement an OFAC sanctions filter on block construction, the miners pointing hashrate at these pools would have no recourse. They would be unknowing accomplices to censorship.
Stratum V2’s job negotiation sub-protocol changes this entirely. A miner running a Bitcoin full node can construct its own block template — selecting transactions from its own mempool based on its own criteria — and propose that template to the pool. The pool verifies that the template is valid and that the miner’s work will be correctly attributed, then allows the miner to hash against its own template.
The implication is profound: even if you mine on a large, centralized pool for payout consistency, you can still exercise sovereign control over the blocks you help produce. The pool gets your hashrate for revenue sharing. You keep your transaction selection sovereignty.
Encrypted Connections: ISPs Cannot Spy or Censor
Stratum V1 sends all data — pool URLs, wallet addresses, hashrate data, job assignments — in unencrypted plaintext. Anyone on the network path between your miner and the pool can see exactly what you are doing. An ISP can identify mining traffic. A state actor can monitor which pool you use. A man-in-the-middle attacker can redirect your hashrate to their own pool without you knowing.
Stratum V2 implements AEAD (Authenticated Encryption with Associated Data) on all communications. This is the same class of encryption used in TLS 1.3 and Signal Protocol. Your ISP sees encrypted traffic. A network attacker cannot forge pool messages. Your mining operation becomes private.
For miners in jurisdictions where Bitcoin mining faces regulatory scrutiny or outright hostility, encrypted connections are not a nice-to-have. They are a security necessity. Even in Canada, where mining is legal and welcome, encrypting your traffic is basic operational hygiene — the same reason you use HTTPS instead of HTTP.
Reduced Pool Power Over Block Construction
The concentration of block construction power in a few pool operators is one of Bitcoin’s most underappreciated systemic risks. When Foundry USA constructs 32% of all blocks, they are making decisions for 32% of Bitcoin’s transaction processing — decisions about fee markets, transaction inclusion, and block composition that should, ideally, be distributed across thousands of independent operators.
Stratum V2 does not eliminate pools. Miners still need pools for variance smoothing (consistent payouts). What V2 does is decouple the economic function of pools (aggregating hashrate and distributing rewards) from the censorship-sensitive function (deciding block contents). Pools handle payouts. Miners handle block construction. Each party does what it should.
This is how mining pool selection intersects with protocol choice. A miner using Stratum V2 with job negotiation on a large pool gets the best of both worlds: consistent payouts from a large pool’s block-finding frequency, and sovereign transaction selection from their own full node.
Current Stratum V2 Adoption
As of Q1 2026, Stratum V2 adoption is accelerating but far from universal.
Pool Support
| Pool | Stratum V2 Status | Notes |
|---|---|---|
| Braiins Pool | Full native support | Pioneered V2; 100% V2 compatible; job negotiation supported |
| OCEAN | DATUM protocol (V2-adjacent) | Custom protocol with similar goals; miner-side block templates |
| Luxor | V2-ready | Infrastructure supports V2 connections |
| DEMAND (DMND) | Full support | First pool built natively on V2 (launched 2025) |
| Foundry USA | Testing | In beta testing; not yet production-ready for all miners |
| AntPool | No | No announced V2 plans |
| F2Pool | No | No announced V2 plans |
| ViaBTC | No | No announced V2 plans |
Hashrate on Stratum V2
Approximately 15-20% of Bitcoin’s network hashrate currently connects via Stratum V2-compatible infrastructure, though the actual percentage using V2’s advanced features (especially job negotiation) is significantly lower. Most miners connecting via V2 are using it for the encryption and efficiency benefits while still accepting pool-constructed block templates.
The adoption trajectory is promising. The Stratum V2 Reference Implementation (SRI) working group projects that by the end of 2026, V2 will be the default protocol for new ASIC firmware shipments, potentially reaching 40-60% of network hashrate. Bitcoin Core v30 added experimental Stratum V2 protocol support, signaling that the broader Bitcoin development community considers V2 adoption important.
Firmware Support
- Braiins OS+ — Full Stratum V2 support with job negotiation. The most mature V2 firmware. Available for Antminer S9, S17, S19, and T series.
- Stock firmware (most ASICs) — Stratum V1 only. However, V2 translation proxies can bridge V1 hardware to V2 pools.
- LuxOS — Stratum V2-ready.
- Bitaxe / open-source miners — Community firmware development for V2 support is ongoing. Check your specific device’s firmware repository for the latest status.
The DATUM Protocol: OCEAN’s Approach
DATUM (Decentralized Alternative Templates for Universal Mining) is OCEAN pool‘s answer to the block template centralization problem. While it shares goals with Stratum V2’s job negotiation, DATUM takes a different architectural approach that is worth understanding on its own terms.
How DATUM Works
With DATUM, a miner runs three components:
- A Bitcoin full node — connected to the Bitcoin network, maintaining a mempool, and constructing block templates.
- A DATUM gateway — software that communicates between the miner’s hardware, the full node, and the OCEAN pool.
- Mining hardware — your ASIC miner, connected to the DATUM gateway instead of directly to a pool.
The flow: your full node constructs a block template from transactions in your mempool. The DATUM gateway formats this template for your mining hardware. Your ASIC hashes against your template. If you find a block, it is submitted to the network directly, with the coinbase transaction paying you (the miner) directly — not the pool.
DATUM vs. Stratum V2 Job Negotiation
| Feature | Stratum V2 (Job Negotiation) | DATUM |
|---|---|---|
| Block template source | Miner proposes, pool approves | Miner constructs and uses directly |
| Pool approval | Required (pool validates template) | Not required (miner builds independently) |
| Coinbase payout | Pool distributes | Direct to miner (non-custodial) |
| Full node requirement | Yes (for job negotiation) | Yes |
| Pool compatibility | Any V2-supporting pool | OCEAN only |
| Fee incentive | None specific | 50% fee discount for DATUM miners |
The key philosophical difference: Stratum V2 job negotiation is a negotiation — the miner proposes a template, and the pool accepts or rejects it. DATUM is unilateral — the miner constructs the template and uses it, period. OCEAN’s model is more radically decentralized, but it is also limited to OCEAN’s ecosystem. Stratum V2 works across any supporting pool.
Both approaches serve the same goal: wresting block construction power away from centralized pool operators and returning it to individual miners. They are allies, not competitors, in the fight for Bitcoin’s decentralization.
Who Should Use DATUM?
DATUM is ideal for miners who:
- Already run a Bitcoin full node (or are willing to)
- Want the most sovereign mining experience available in a pooled context
- Are comfortable with the technical requirements of running a DATUM gateway
- Want non-custodial block rewards (paid directly in the coinbase transaction)
- Believe in OCEAN’s mission and want to support its growth
For the average home miner who just wants to plug in an ASIC and start earning, DATUM adds complexity. But for the technically inclined Bitcoiner — the mining hacker — it is the most sovereign way to mine in a pool today.
How to Use Stratum V2: Setup Guide
Ready to upgrade? Here is how to get your mining operation running on Stratum V2.
Option 1: Braiins OS+ Firmware (Easiest)
If you run Antminer S9, S17, S19, or T-series hardware, the fastest path to Stratum V2 is flashing Braiins OS+ firmware.
- Download Braiins OS+ from braiins.com/os/plus for your ASIC model.
- Flash the firmware using Braiins Toolbox (available for Linux, macOS, and Windows). The process takes about 5 minutes per device.
- Configure your pool in the Braiins OS+ web interface. Set your pool URL to Braiins Pool’s Stratum V2 endpoint:
stratum+tcp://v2.stratum.braiins.com:3333 - Enable autotuning (optional but recommended) — Braiins OS+ dynamically adjusts chip voltage and frequency for optimal efficiency.
- Verify V2 connection — check the “Stratum” section in the web interface. It should show “V2” as the active protocol.
Option 2: Stratum V2 Translation Proxy (For V1 Hardware)
If you cannot flash custom firmware (warranty concerns, unsupported hardware, etc.), you can run a Stratum V2 translation proxy on a local computer. This proxy sits between your V1 miner and the V2 pool, translating the protocol in real time.
- Install the SRI Translation Proxy — available from the Stratum V2 Reference Implementation GitHub repository. Runs on Linux, macOS, or a Raspberry Pi.
- Configure the proxy with your V2 pool endpoint and your worker credentials.
- Point your ASIC miners at the proxy’s local address (e.g.,
stratum+tcp://192.168.1.100:34255). - Your miners speak V1 to the proxy, and the proxy speaks V2 to the pool. You get encryption and bandwidth benefits without modifying your miner firmware.
Note: the translation proxy does not support job negotiation. For full V2 benefits including miner-side block template construction, you need V2-native firmware.
Option 3: Job Negotiation (Full Sovereignty)
This is the advanced configuration for miners who want complete control over their block templates.
- Run a Bitcoin full node — Bitcoin Core v28+ recommended. Ensure it is fully synced and connected to the network.
- Install Braiins OS+ on your ASIC hardware.
- Configure job negotiation in Braiins OS+ settings, pointing it to your local Bitcoin node’s RPC endpoint.
- Connect to a V2 pool that supports job negotiation (Braiins Pool, DEMAND).
- Your miner now constructs block templates from your node’s mempool and proposes them to the pool. The pool validates and accepts the work.
This setup requires more technical knowledge and a dedicated machine running Bitcoin Core (approximately 700+ GB of disk space for the full blockchain). But the result is the most sovereign form of pooled mining possible: you choose the transactions, you verify the chain, and you contribute to Bitcoin’s decentralization at the protocol level.
Option 4: OCEAN DATUM (Maximum Decentralization)
For the ultimate in miner sovereignty within a pooled framework:
- Run a Bitcoin full node — fully synced Bitcoin Core.
- Install the DATUM gateway from OCEAN’s GitHub repository.
- Configure the gateway with your Bitcoin node RPC credentials and your OCEAN worker credentials.
- Point your ASIC miners at the DATUM gateway’s local stratum endpoint.
- Mine with full sovereignty — your node builds templates, your hardware hashes, and your block rewards go directly to your wallet.
What This Means for Home Miners
If you are a home miner reading this, you might be wondering: does any of this apply to me, or is it only for warehouse-scale operations?
It applies to you. Arguably, it applies to you more than anyone.
Privacy
Home miners have the most to gain from encrypted connections. Your mining traffic flows through your home internet connection — the same ISP that knows your name, address, and billing information. With Stratum V1, that ISP can see exactly which pool you are mining on, how much hashrate you are contributing, and your wallet address. With Stratum V2, all they see is encrypted traffic. For miners who value privacy — and if you are mining Bitcoin at home, you probably do — this is a significant upgrade.
Bandwidth
Home internet connections, especially in rural Canada, are not always generous with bandwidth. Stratum V2’s 60-70% reduction in mining protocol traffic is meaningful if you are running multiple ASICs on a residential connection, especially one shared with family streaming, video calls, and other household use. Less bandwidth consumed by mining means less impact on your household internet quality.
Efficiency
The 1.42 ms block-switching latency (vs. 325 ms on V1) means your ASIC spends more time hashing against valid work and less time working on stale blocks. Over a year, Braiins estimates this recovers approximately 4.9 hours of hash power. For a miner paying residential electricity rates, every watt-hour counts. Stratum V2 makes your hardware more productive without consuming any additional power.
Sovereignty
This is the big one. If you are a home miner, you are likely motivated by more than profit. You are here because you believe in Bitcoin’s decentralization, because you want to contribute to network security, because you want to earn non-KYC Bitcoin, or because you want to heat your home while stacking sats. Stratum V2 lets you take that conviction to its logical conclusion: running a full node, constructing your own block templates, and ensuring that your hashrate is not being used to censor transactions or exclude addresses you believe should be included.
For Bitaxe and open-source miner operators, who are already on the frontier of decentralized hardware, Stratum V2 and DATUM are the protocol-layer complement to their hardware-layer sovereignty. Open-source hardware running a sovereign mining protocol, connected to a non-custodial pool — that is the full stack of decentralized Bitcoin mining.
The Road Ahead: Stratum V2 Adoption Timeline
Where does V2 go from here? Based on current momentum and announced plans:
2026 Milestones
- Q1-Q2 2026: Major pools announce V2 support. Foundry USA expected to move from testing to production. More pools add V2 endpoints.
- Q3 2026: V2 becomes the default protocol in new ASIC firmware shipments. Bitmain and MicroBT expected to include V2 support in stock firmware for new models.
- End of 2026: Projected 40-60% of network hashrate on Stratum V2. Job negotiation usage still likely below 10%, but growing.
Remaining Challenges
Inertia. Stratum V1 works. Miners and pools have built their infrastructure around it. Switching requires firmware updates, proxy configurations, and operational changes. For large operations with thousands of machines, the migration cost is non-trivial.
Job negotiation complexity. Running a full node and configuring job negotiation requires technical knowledge that many miners do not have. Until the tooling becomes plug-and-play simple, most miners will use V2 for encryption and efficiency while still accepting pool-constructed templates.
Pool resistance. Some pools may be reluctant to support job negotiation because it reduces their control over block construction — which some pools may view as a competitive advantage (or a revenue source, in the case of MEV-like transaction ordering). Pools that resist V2 are telling you something about their priorities.
Firmware fragmentation. Not all ASIC models have V2-capable firmware. Braiins OS+ covers major Antminer models, but MicroBT Whatsminers, Canaan Avalons, and many newer ASICs still lack V2-native firmware options.
The Long-Term Vision
The endgame is clear: a Bitcoin network where every miner encrypts its pool connection, selects its own transactions, and contributes to a genuinely decentralized block construction process. Pools become what they should be — economic aggregators for variance smoothing — rather than what they have become: centralized gatekeepers of Bitcoin’s transaction processing.
This is not a pipe dream. The protocol exists. The firmware exists. The pools exist. The only remaining variable is adoption — and adoption is a function of education, tooling, and community will.
FAQ
Is Stratum V2 backwards compatible with V1?
Not directly, but translation proxies bridge the gap. You can run V1 hardware behind a V2 proxy, which translates between the protocols in real time. Your old ASICs do not need new firmware to benefit from V2’s encryption — they just need a proxy running on your local network. However, job negotiation requires V2-native firmware.
Does Stratum V2 increase my mining profits?
Yes, modestly. The efficiency gains from reduced bandwidth, faster block switching (recovering ~4.9 hours of hash power annually), and reduced stale share rates can increase net profits by up to 7.4% according to Braiins’ measurements. The exact improvement depends on your specific setup, internet connection, and distance from the pool’s servers.
Can I use Stratum V2 with any pool?
No. Only pools that have implemented V2 support can accept V2 connections. As of early 2026, Braiins Pool has full native support, DEMAND (DMND) was built on V2, Luxor is V2-ready, and Foundry USA is testing. OCEAN uses its own DATUM protocol, which shares V2’s goals but uses different technology. Most other major pools (AntPool, F2Pool, ViaBTC) do not yet support V2.
Do I need to run a full node for Stratum V2?
No — only if you want to use job negotiation (miner-side block template construction). For the encryption and efficiency benefits alone, you just need V2-compatible firmware or a translation proxy. Running a full node is the advanced path for miners who want sovereign transaction selection.
Is DATUM better than Stratum V2?
They serve different but complementary purposes. DATUM is OCEAN’s specific implementation for non-custodial, miner-sovereign block construction within OCEAN’s pool. Stratum V2 is a universal protocol that works across multiple pools. If you mine on OCEAN and run a full node, DATUM gives you maximum sovereignty. If you want V2 benefits across different pools, Stratum V2 is the universal standard. Both advance decentralization — choosing either one over Stratum V1 is a win.
What happens if my V2 connection drops — do I lose work?
No. Stratum V2 includes connection resilience features, and most V2-capable firmware will automatically fall back to a backup pool (which can be V1 or V2). You may experience a brief interruption while reconnecting, but submitted shares are not lost. Configure a backup pool in your miner settings to minimize any potential downtime.
The Protocol Matters
Bitcoin miners obsess over hashrate, efficiency, power costs, and pool fees. These are the variables that determine short-term profitability. But the mining protocol — the software layer between your hardware and the network — determines something more important: who controls Bitcoin’s block construction.
For over a decade, that control has been silently concentrated in the hands of a few pool operators running Stratum V1. Stratum V2 and DATUM are the corrections. They return transaction selection to individual miners. They encrypt connections that should never have been plaintext. They make pooled mining compatible with Bitcoin’s founding principle: decentralization.
At D-Central Technologies, decentralization is not a feature we list on a product page. It is the reason we build, repair, and sell mining hardware. From open-source miners like the Bitaxe to the protocol layer with Stratum V2, every layer of Bitcoin mining should be as decentralized as the network itself.
Upgrade your protocol. Run a full node. Choose a pool that gives you sovereignty. Every hash matters — make yours count.
Ready to start mining? Browse our complete catalog of miners and accessories, or read our mining pool comparison to find the right pool for your operation.