Miner Signaling via DMND Stratum V2: You Decide What to Signal
The short version:
- Since 25 June 2026 (block 955,318), miners on DMND using the Stratum V2 Job Declaration Protocol build their own block templates on Bitcoin mainnet. That includes the nVersion field. You choose your transactions and you choose what your blocks signal, against BIP-110, for it, or for any proposal, current or future.
- DMND is agnostic on miner signaling. We will never override, filter, or edit the version bits or transaction selection of a miner declared template. Your block reaches the chain exactly as you built it. Always.
- DMND follows Bitcoin consensus. Job Declaration gives you full control over what to signal and what not to signal. For the default setting, DMND positions only with consensus: we will never switch a pool endpoint to signal for or enforce a BIP that has not been accepted through Bitcoin's consensus process. We do not front run consensus, and we do not use aggregated hashrate to lobby.
- Decisions with financial impact for miners belong to miners, not the pool. Any protocol change that affects what a miner earns per block is a decision each miner must make for themselves. A pool operator has no business making it for them.
That is the whole position: the miner is sovereign over their own blocks, and the pool is neutral infrastructure.
One thing to weigh before setting bit 4
That last point is not abstract. BIP-110 is a live example, and we owe miners honesty about incentives.
BIP-110 restricts data carrying transactions, and those transactions pay fees. A template built under BIP-110 rules excludes a fee paying transaction class, so miners enforcing it earn less per block, and if it activated network wide that fee revenue would simply be gone. With the subsidy at 3.125 BTC and halving forever, fees are the industry's long term survival variable.
Supporters counter that the trade off buys lower node costs and a chain focused on money. Both are legitimate positions. Our point is narrower: that trade off belongs to the miner whose block it is, not to a pool operator deciding for everyone. On DMND, it's your call.
Why miners have never had a voice
Under legacy Stratum V1, the pool constructs the block template: transaction selection, coinbase, and the nVersion bits in the header. Miners contribute hashrate to blocks they never see the inside of. Millions of machines, thousands of operators, and in the end a handful of pool level votes.
So when you look at BIP-110 signaling data today, under 1% of blocks with a mandatory signaling window beginning at block 961,632 in August, you are not looking at miner opinion. You are looking at pool operator opinion. Actual miner preference has never been measurable, because most hashrate physically cannot express one.
What Job Declaration changes
With Job Declaration, the miner constructs the template. Since our first live JD block on 25 June, this runs in production on DMND: your transactions, your coinbase, your nVersion. Set bit 4 if you support BIP-110. Leave it unset if you don't. Signal for whatever comes next.
This was the design intent of Stratum V2 from day one: decentralize template construction and remove the pool as a single point of protocol politics. Signaling from JD miners is real preference data, block by block, miner by miner. That is a feedback loop the development community has been missing for over a decade.
DMND is the first Stratum V2 mining pool with full Job Declaration Protocol support. Build your own block. Set your own bits. join.dmnd.work