Mining

Proof-of-work checkpoints with dedicated Stratum and CPU/GPU mining.

WildRoot miners produce the checkpoint chain, earn the fixed coinbase subsidy and move activated application history toward hard finality. Transaction usability remains DAG-driven rather than block-driven.

Subsidy1 WR forever

Target60 seconds

Maturity60 blocks

HalvingNone

Stratum

Solo and pool operation share the dedicated mining interface.

Stratum binds to loopback by default. Operators who want to run a public pool or remote miner endpoint must explicitly configure exposure, firewalling/NAT and any surrounding transport security.

In solo mode, accepted block work pays the authorized worker. In pool mode, block rewards pay the configured pool address while sub-network share accounting and participant distribution remain the pool operator's responsibility.

Current mining defaults

Default Stratum   stratum+tcp://127.0.0.1:17323
Operation modes    solo | pool
Block subsidy      1 WR
Coinbase maturity  60 PoW blocks
Target interval    60 seconds

Reward service fee

Optional at the Stratum service layer, zero by default.

Independent mode settings

Solo and pool modes each have a configurable block-reward service fee expressed in basis points and defaulting to zero.

Canonical optional output

When a non-zero fee is active, the coinbase can contain one optional second canonical output to the configured service-fee address.

Fixed subsidy preserved

The sum of coinbase outputs remains exactly the fixed 1 WR block subsidy. Ordinary one-output coinbases remain canonical.

Mining backends

Standalone miner and desktop mining share the same mining library.

wildroot-miner is the standalone miner. The GUI links the same miner library directly rather than spawning the executable. The mining stack supports CPU and GPU paths, explicit device selection and multi-device operation.

The Windows build can install a CUDA backend with compiled targets for sm_75, sm_80, sm_86, sm_89, sm_90 and sm_120, plus compute_120 PTX. OpenCL remains available for compatible devices outside that CUDA path.

CUDANative sidecar/backend with current Windows fat-binary targets

OpenCLPortable GPU path with event-polled kernel completion

CPUReference/fallback mining and protocol test path

Template APICompatibility getblocktemplate / submitblock workflow

DAG changes do not invalidate useful work by themselves

Transaction usability is DAG-driven, so the miner does not need to abandon active PoW work merely because the open DAG changed. The next template can commit the current accepted application state.

Only active best-tip acceptance counts as mined

Miner UI status calls a block mined only after the node confirms the submitted hash became the active best checkpoint tip; stale or side-branch solutions are not counted as successful mined blocks.