Traqueur de déploiement Stratum V2
Réponse rapide
Stratum V2, c'est deux choses différentes, et les confondre est la plus grande erreur qu'on fait à son sujet. SV2-le-transport — chiffrement, authentification qui empêche le détournement de hashrate, minage par en-tête seul, moins de bande passante — est EN DIRECT et livré : BraiinsOS+ et (depuis juin 2026) AxeOS le parlent nativement, et n'importe quel mineur SV1 peut atteindre un pool SV2 via un proxy traducteur. Le SV2 Job Declaration — la partie qui décentralise vraiment le minage en laissant le MINEUR construire le template de bloc au lieu du pool — est le dernier kilomètre difficile, et il est passé de la théorie à la réalité le 25 juin 2026 quand le pool DMND et GoMining ont miné le bloc mainnet 955 318 à partir d'un template déclaré par le mineur. Mais c'est encore une pile assemblée à la main (votre propre nœud + un Template Provider en side-car + un Job Declarator Client) pointée vers, en pratique, le seul pool de production qui l'honore.
Le SV2 nu, sans Job Declaration, n'est qu'un tuyau meilleur et plus sûr — il ne décentralise rien. La décentralisation, c'est le Job Declaration, et à la mi-2026 elle est réelle mais pas encore clé en main : un pool en direct (DMND), un chemin de template expérimental dans Bitcoin Core, et aucun firmware grand public qui fait le JD tout seul. Ne croyez aucune affirmation selon laquelle un firmware ou un pool vous donne des « templates construits par le mineur » sans vérifier qu'il exécute un Job Declarator.
Les 6 rôles de SV2
| Rôle | Ce qu'il fait | Construit des templates ? | Spec |
|---|---|---|---|
| Mining DeviceMiner | The endpoint doing the hashing (ASIC firmware or hashing app). Speaks the Mining Protocol to a pool/server over the encrypted SV2 transport, receiving jobs and submitting shares. | nonOnly hashes assigned work; builds no templates. Decentralization comes from whatever feeds it jobs. | stable |
| Pool (Mining Server)Pool | Server-side role running the Mining Protocol: opens channels, distributes work, accounts shares, pays rewards. In a job-declaration deployment it is reduced to share-accounting + payout. | activateur seulementPlain SV2 pooling still means the POOL chooses transactions. Only decentralizes if the pool also runs a Job Declarator Server. | stable |
| Translator Proxy (SV1↔SV2)tProxy | Sits between legacy SV1 mining devices and an SV2 pool, translating SV1 JSON-RPC to the SV2 binary/encrypted protocol so non-native hardware can reach an SV2 endpoint. | nonA compatibility shim for the transport. Relevant to decentralization only when paired with a local JDC supplying templates upstream. | stable |
| Job Declarator ClientJDC | Runs on the MINER's side. Takes a candidate template from a local Template Provider, then declares that transaction set to the pool's Job Declarator Server before mining it. | décentraliseThe core decentralization role — how a miner asserts its own transaction selection instead of accepting pool-dictated work. | draft |
| Job Declarator ServerJDS | Pool-side counterpart to the JDC. Validates the miner-declared template (transactions, fees, coinbase), approves it, and coordinates with the Mining Server so the miner's own block goes forward. | décentraliseA pool MUST run a JDS for miner-side template building to be honored. Without a live JDS, Job Declaration is theoretical. | draft |
| Template ProviderTP | Generates candidate block templates (the transaction selection) and streams them to the JDC. Normally a Bitcoin full node — now via Bitcoin Core's experimental IPC Mining interface + an external SV2 sidecar. | décentraliseWhere the actual transaction set is built. Miner-run TP + JDC returns block construction to the miner; a pool-run TP defeats the purpose. | stable |
Implémentations — ce qui fonctionne réellement aujourd'hui
| Implémentation | Rôles SV2 | Version | Maturité | Job Declaration en direct ? |
|---|---|---|---|---|
| Stratum Reference Implementation (SRI) | Pool, JDS, JDC, Translator Proxy, TP sidecar, test Mining Device — ALL roles | Libraries repo ~v1.11.0 (2024, split into stratum-mining/stratum + sv2-apps roles); v1.0.0 milestone Mar 2024 | beta | JD : partial |
| The canonical, most complete SV2 codebase and the substrate DMND is built on. Full JD works in SRI and has now produced real mainnet blocks via DMND — but SRI itself is a reference/beta stack you hand-assemble, not turnkey consumer firmware. | ||||
| Braiins (BraiinsOS+ / Braiins Pool) | Mining Device (native SV2 client), Pool (SV2 transport endpoint) | BraiinsOS+ native SV2 client (2026); Braiins Pool publishes V1 + V2 endpoints | production | JD : no |
| TRANSPORT ONLY. BraiinsOS+ is the only commercial ASIC firmware with a native SV2 client (S9/S19/S21/S21 XP connect without a proxy) — encrypted, authenticated, header-only mining. Braiins' own academy still frames miner-built templates as a FUTURE capability: Job Declaration is NOT a generally available Braiins customer feature. | ||||
| Bitcoin Core — IPC Mining interface (TP path) | Template Provider (via generic Mining IPC, not SV2-native code) | Core 30.0 (Oct 2025) shipped the EXPERIMENTAL IPC Mining interface; 30.1 relaxed the -m requirement | experimental | JD : partial |
| The SV2-in-Core PR (#29432) was CLOSED — Core rejected embedding SV2. Instead it exposes a generic Mining interface over Cap'n Proto IPC; run multiprocess `bitcoin-node -m -ipcbind=unix` and an external SV2 TP sidecar (Sjors Provoost) connects to it. So a forked Core is no longer mandatory — pristine Core 30.x + sidecar works — but the interface is experimental and needs the sidecar. | ||||
| DMND (DEMAND) Pool | Pool (Mining Server), Job Declarator Server; supports miner-side JDC + TP | Launched Nov 2025 as first V2-native pool; first live JD block 2026-06-25 | production | JD : yes |
| 🔴 THE milestone: on 2026-06-25 DMND + GoMining mined mainnet block 955,318 using SV2 Job Declaration — the MINER, not the pool, selected transactions and built the template. Built on SRI. The first and (as of mid-2026) effectively only pool honoring job-declared work in live production. Still early: one flagship miner, not yet mass turnkey. | ||||
| AxeOS / ESP-Miner (Bitaxe) | Mining Device (native SV2 client) | Native SV2 early-access Mar 2026; stable in v2.14.0 (June 2026) | beta | JD : no |
| Native SV2 as a Mining Device only: binary protocol, Noise/ChaCha20-Poly1305 encryption, standard mining-channel messages, tested on BM1370 Bitaxe against the SRI reference pool. Speaks the SV2 TRANSPORT natively (no translator proxy) but does NOT do Job Declaration — it hashes assigned work. The second native-SV2 firmware family after BraiinsOS+. | ||||
Verdict de bout en bout
Un mineur peut-il exécuter le Job Declaration complet aujourd'hui ? PARTIAL. What works: a production pool (DMND) runs a live Job Declarator Server accepting miner-declared templates (proven on-chain); you can source templates from a pristine Bitcoin Core 30.x node via the experimental IPC Mining interface + Sjors' TP sidecar (a forked Core is no longer required); SRI provides working JDC/JDS/TP/translator roles. What is missing: it is a hand-assembled SRI/sidecar stack, not turnkey — you run your own node + TP sidecar + JDC and point them at a JD-capable pool, and effectively only ONE major pool (DMND) honors declared jobs in production today.
Firmware SV2 natif. Two firmware families speak SV2 natively (transport, no translator proxy) in 2026: BraiinsOS+ (industrial Antminers — the only commercial firmware with a native client, transport-only) and AxeOS/ESP-Miner for Bitaxe (native SV2 since v2.14.0, Mining Device only). Everything else — stock Antminer/Whatsminer, VNish, LuxOS — is SV1 and needs the SRI Translator Proxy. Native transport is NOT Job Declaration: none of these firmwares do JD themselves; JD requires a separately-run JDC + Template Provider co-located with the miner.
Le plus grand écart. Turnkey, miner-side Job Declaration integrated into consumer firmware and pools. The pieces exist and interoperate (Core IPC TP, SRI JDC/JDS, one live production JD pool), but a normal miner still cannot flip a switch — broad pool-side JDS adoption and firmware-integrated JD are the missing last mile.
Données ouvertes (CC BY 4.0) : CSV · JSON · API : /wp-json/dc/v1/stratum-v2-deployment
Produits, réparations et guides connexes
- comment D-Central diagnostique les réparations ASIC
- bibliothèque de dépannage ASIC
- manuels ASIC et guides de réparation
- hashboards de remplacement
- cartes de contrôle ASIC
- blocs d’alimentation ASIC
- comparer les specs dans la base de mineurs ASIC
- comparer les specs des mineurs ASIC
- base de mineurs ASIC
- services de réparation ASIC
- specs et rentabilité de l’Antminer S19
- acheter un Antminer S19 testé
- guide d’entretien Antminer S19
- service de réparation Antminer S19
- specs de l’Antminer S21
- Bitmain Antminer S21
- guide d’entretien Antminer S21
- puce BM1370BC pour S21 Pro
- specs de l’Antminer S9
- Bitmain Antminer S9
- guide d’entretien Antminer S9
- ensemble de pièces de réparation de hashboard S9
- specs du Whatsminer M30S
- guide de réparation Whatsminer
- MicroBT Whatsminer M30S++
- conduit d’évacuation Whatsminer M3x
Dernière révision: 27 juillet 2026.