DMND Monitoring API — Your mining data, connectedMonitor your hashrate, workers, earnings, and payouts with DMND’s read-only API. Get started with clear explanations and copyable examples.DMND. The DMND Monitoring API puts your hashrate, workers, shares, fees, earnings, and confirmed payouts straight into whatever you already use to run

Optional, off by default. The practical payoff of building your own blocks. Once you're building your own blocks (setup guide here), you also control which transactions your templates favor. The DMND Client exposes an API to do exactly that. Build the block, decide what gets bumped. What it

A single guide from bare node to mining your own blocks. Keep an eye on the client README. The canonical, always-current setup reference lives at https://github.com/dmnd-pool/dmnd-client. The client ships new releases regularly, so if a flag, port, or step ever differs from what

This guide explains how version-bits signaling actually works, how it flows through a DMND Job Declaration setup, and what to consider before signaling for any deployment — current or future. It applies to any BIP that uses version-bits activation; only the bit number changes. How signaling works Soft-fork

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

DMND has mined the first known Bitcoin block produced using Stratum V2 Job Declaration. Block 955,318 was mined on mainnet for GoMining, who became the first miner to build and declare its own block template and have it mined through a pool. This is the part that matters. For