How to Enable Stratum V2 Without Flashing Your Miner (SRI Translation Proxy Setup)

What the proxy does — and what it doesn’t

Two firmware families speak Stratum V2 natively: BraiinsOS+ on industrial Antminers, and AxeOS / ESP-Miner (v2.14.0+, since June 2026) on the Bitaxe. D-Central’s DCENT_OS contains a native V2 implementation in source, but it is default-off and readiness-gated while live submit/accept soak remains pending. Everything else — stock Antminer and Whatsminer, VNish, LuxOS — is Stratum V1 only. For that large installed base, reflashing is the only way to get SV2 in the firmware — unless you put a translator in front of the miner instead.

The SRI Translation Proxy (tProxy) is part of the Stratum Reference Implementation — the open-source reference project the entire SV2 ecosystem stands on. It sits on your local network: your SV1 miners connect to it over ordinary stratum, and it re-speaks that connection to your pool as SV2.

What you need

• A small always-on Linux box on the same network as your miners — a Raspberry Pi 4/5 or any mini-PC is plenty (the proxy is light).
• Your pool’s SV2 connection details: address, port, and its authority public key. Get these from your pool. (Braiins Pool ships as the backup upstream in the reference project’s own example config, so SV2 pools are real and available today.)
• Your existing miners on stock, VNish or LuxOS — no firmware change.

Step 1 — Install the Translation Proxy

The tProxy lives in the reference project’s applications repo, stratum-mining/sv2-apps (current release v0.6.0, July 2026), under miner-apps/translator. Build it from source with Rust/Cargo, or run the project’s Docker image — always follow the repo’s current build instructions rather than a copied command, because they evolve between releases. Use the example config at miner-apps/translator/config-examples/mainnet/tproxy-config-hosted-pool-example.toml as your starting point.

Step 2 — Configure it

Here are the keys that matter, taken from the real example config (placeholders where a value is pool-specific — don’t invent those, get them from your pool):

# --- Where your SV1 miners connect (the proxy's listener on your LAN) ---
downstream_address = "0.0.0.0"
downstream_port    = 34255

max_supported_version = 2
min_supported_version = 2

# --- Your Stratum V2 pool (primary). Get these three values from your pool. ---
[[upstreams]]
address          = "pool.example.com"     # your SV2 pool host
port             = 3333
authority_pubkey = "<your pool's authority public key>"
user_identity    = "<your pool username or BTC address>"

# --- Optional second pool = automatic failover ---
[[upstreams]]
address          = "<backup pool host>"
port             = 3333
authority_pubkey = "<backup pool authority public key>"
user_identity    = "<your backup username>"

# --- Difficulty / vardiff ---
[downstream_difficulty_config]
min_individual_miner_hashrate = 10_000_000_000_000.0  # your weakest miner (10 TH/s shown)
shares_per_minute             = 6.0
enable_vardiff                = true

• downstream_port (default 34255) is the port your miners will point at.
• Each [[upstreams]] block is a pool. The authority_pubkey is how the proxy cryptographically verifies it’s talking to the genuine pool — that’s the “authenticated” half of SV2. Add a second [[upstreams]] block for automatic failover.
• user_identity is your pool username (many pools use your BTC address).
• Set min_individual_miner_hashrate to your weakest miner’s hashrate so vardiff behaves; leave enable_vardiff = true for normal pool mining.

Step 3 — Point your miners at the proxy

In each miner’s pool settings (the stock, VNish or LuxOS web UI), set the pool URL to:

stratum+tcp://<your-proxy-LAN-IP>:34255

…with your usual worker name. That’s the whole change on the miner — no firmware touched. To undo it later, just point the miner back at your pool’s direct URL.

Step 4 — Verify it’s working

• Watch the tProxy logs: you should see your downstream miners connect and an upstream SV2 channel open to the pool.
• The proxy exposes an optional monitoring endpoint (monitoring_address, default port 9092) with live channel data.
• Your shares should appear at the pool under your username as usual — now carried over an encrypted, authenticated SV2 link.

Prefer SV2 in the firmware itself?

If you’d rather not run a separate box, the alternative is flashing SV2-native firmware. DCENT_OS — D-Central’s own GPL-3.0 firmware, with guarded experimental S9 XIL and S19j Pro XIL artifacts — contains a default-off V2 implementation whose live submit/accept readiness remains unproven. It’s experimental beta firmware and a bad flash can brick a miner, so keep a recovery path ready — the proxy route above avoids writing experimental firmware to the miner, though it still requires normal network and host hardening. DCENT_OS stands on the shoulders of the Stratum Reference Implementation and the firmwares (BraiinsOS+, AxeOS) that proved this work possible.

Frequently asked questions

Configuration keys and version above are grounded in the live Stratum Reference Implementation (github.com/stratum-mining/sv2-apps, miner-apps/translator) as of July 2026 — not invented. Verify current build steps and any pool-specific values against your pool and the project’s docs before you rely on them. D-Central credits the Stratum Reference Implementation and the open-source firmwares that opened this space.