• 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.

I'm curious what this means:

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.

I get the sense that BIP 110 supporters feel that the status quo is an active stance, but then again I've been told a number of times that the Bitcoin chain will just naturally follow the BIP 110 chain, so maybe a default for the status quo is fine.