MineMaster 1.4.18 — KRig reporting reliability

MineMaster 1.4.18 — KRig reporting reliability

• Recognize KRig pool connection/disconnection events and its startup version. Pool details show the endpoint and original event time.
• Classify KRig failures and warnings correctly in central logs. Statistics API failures are warnings; they do not stop mining or invent readings.
• Keep KRig statistics working through Windows clock corrections using monotonic run-age checks. Frozen or wrong-run responses remain rejected.
• Show when share counters were observed, distinguishing current from last-reported readings in both the desktop and admin. The API exposes the same share quality and declares KRig's 60-second reading freshness window.

Engine versions and existing rig assignments are unchanged. All four pinned engines matched official latest stable releases. Verification: 149 client tests, 145 backend tests, both production builds, and desktop/narrow simulated UI checks. FrontDesk's live KRig API rates and accepted shares matched its logs before this release; longer-term stability and Windows Security behavior remain hardware observations, not guarantees.

MineMaster 1.4.17 — KRig pool configuration fix

MineMaster 1.4.17 — KRig pool configuration fix

KRig requires SSL when connecting to Kryptex. This release rejects plaintext Kryptex settings and the known TCP ports in both primary and backup pools, before a miner can fail during startup. Select TLS and port 8049 for Quantus or 8048 for Pearl. New KRig selections default TLS on, with matching admin guidance and backend validation. Third-party TCP pools remain supported.

The saved Quantus/Pearl KRig profiles were corrected on production. FrontDesk successfully installed 1.4.16 automatically and launched KRig 1.5.6 after the SSL correction; CPU Nanominer remained independent. The mining engines are unchanged in 1.4.17. Existing rig assignments remain unchanged.

Published through the normal stable automatic-update channel. Validation: 146 client tests and 143 backend tests pass, including primary/backup transport and port checks. Real Windows launch and fresh API hashrate were observed; this does not establish overnight stability or future Windows Security behavior.

MineMaster 1.4.16 — KRig support

MineMaster 1.4.16 — KRig support

This release adds KRig 1.5.6 for GPU Quantus and Pearl on Windows/Linux x64. Existing CPU/GPU engine choices stay unchanged. KRig does not mine Ravencoin or Monero; Nanominer and the other existing engines remain available.

• Select KRig in GPU settings on the desktop or admin, save a coin profile and deliver it to a client advertising KRig support.
• Preserve scoped Play/Pause, configuration acknowledgments, diagnostics, explicit repair, file logging and bounded opt-in crash recovery.
• Read aggregate hashrate and share counters from KRig's loopback HiveOS API. Missing, failed or frozen responses do not become zero or fresh samples. CPU mining runs independently.
• Verify official archive/executable hashes and retain upstream licensing notices. No changes to Windows Security, executable names or quarantine behavior.
• KRig's published developer fees are 0% on Kryptex and 3% on other pools; pool fees are separate. GPU models and driver/runtime requirements still need a trial. Linux AMD requires HIP; MineMaster does not install drivers/runtime packages.

Published as the latest stable release. Supported clients automatically download and install it through their normal update checks; existing mining engine selections remain unchanged. KRig must be explicitly selected for a rig. Automated tests use fake processes and disposable data; they do not establish Windows permission, real pool acceptance or throughput.

MineMaster 1.4.15

MineMaster 1.4.15

• A first file check of a packaged XMRig, Nanominer, or SRBMiner copy reports that it installs on first start, instead of a missing-file error.
• Windows start and stop list managed SRBMiner processes once when none match, accept UTF-16 output, and retry one transient failure. The panel shows a short reason instead of the PowerShell command.
• CPU and GPU stops stay independent. Only a managed SRBMiner whose log path belongs to that slot can be reclaimed.

The accompanying admin labels that packaged state as “packaged, installs on first start.”

SRBMiner 3.7.1, Nanominer 3.10.0 and XMRig 6.26.0 remain pinned. Automated checks use inert downloads, fake processes and disposable data; real Windows installation, policy blocks and GPU faults still need on-site validation.

MineMaster 1.4.14

MineMaster 1.4.14

• Keep updater ownership until canceled installation preparation finishes, preventing a new check/download from overlapping stop/save cleanup.
• Cancel late background downloads if their update check finishes after updater shutdown; observe errors without leaving a watchdog behind.
• Preserve automatic installation of verified Windows/Linux updates and explicit retry after canceled or failed attempts.

The accompanying backend fixes clock-offset history expiry: monitor sweeps now use engine-specific limits and the original bounded report clock, and missing-timestamp reports close previous intervals consistently. Current telemetry freshness is unchanged and old chart buckets are not rewritten.

SRBMiner 3.7.1, Nanominer 3.10.0 and XMRig 6.26.0 remain pinned. Automated checks use inert downloads, fake processes and disposable data; real Windows installation, policy blocks and GPU faults still need on-site validation.

MineMaster 1.4.13

MineMaster 1.4.13

• Record native starts, parent exits and confirmed/failed Stops with process/run IDs in the existing rotating diagnostic logs. Launch wallets, passwords and arguments are not added to these records.
• Report when a previously observed miner log disappears, clear stale partial lines, and resume reading safely when the file returns.
• Prevent synchronous/asynchronous logging callback failures from interrupting file monitoring or native controls.

Paired backend fix: Stop, pause and removed-process transitions close chart history consistently with the existing five-minute clock tolerance, preserving original sample times and missing-versus-zero semantics.

Engine versions remain SRBMiner 3.7.1, Nanominer 3.10.0 and XMRig 6.26.0. No profile, protection setting, automatic recovery policy or forced fleet installation is changed. Hardware/driver/file-policy faults still require observation on the affected machine.

MineMaster 1.4.12

MineMaster 1.4.12

• Update SRBMiner-MULTI to 3.7.1 with verified Windows/Linux upstream archives and runtime files. Upstream reports Quantus improvements on AMD/Intel GPUs; Nanominer 3.10.0 and XMRig 6.26.0 remain current.
• Keep Stop available when a parent miner has exited but owned children may remain, including disabled slots or missing GPU inventory. Show Stop required, prevent misleading quick Start, and keep Repair blocked until ownership is resolved.
• Attempt verified managed-survivor cleanup during the same Stop when a parent exits during shutdown, instead of requiring another attempt.
• Preserve unresolved process-ownership errors across engine selection changes and immediately reconcile diagnostics after confirmed Stop.

No mining profiles, clock/power settings, protection policies or automatic retry policies are changed. The update does not establish that missing miner files were quarantined or resolve hardware/driver errors. Windows/Linux packages are verified without executing miners or installers.

MineMaster 1.4.11

MineMaster 1.4.11

• Stop checking/installing unused engines at startup based on legacy CPU/GPU slot names. Prepare and verify the selected engine when launching or performing explicit maintenance.
• Prevent old XMRig file diagnostics from appearing as Nanominer CPU failures after an engine change.
• Keep process-exit and failed-Stop errors visible until resolved. A late file check cannot overwrite a newer launch or lifecycle failure.
• Make desktop Stop All check both slots for surviving managed processes, including slots reported stopped.
• Recognize managed SRBMiner survivors whose command line starts with a basename, using the resolved executable path and exact slot log argument to establish ownership. Fix Windows argument splitting after unquoted trailing backslashes.

Engines remain SRBMiner 3.7.0, Nanominer 3.10.0 and XMRig 6.26.0. No miner profile, automatic crash-recovery policy, clock or antivirus setting is changed.

MineMaster 1.4.10

MineMaster 1.4.10

Windows SRBMiner can leave a replacement process alive after its original parent exits. MineMaster now checks for surviving managed instances before launching or repairing, preventing duplicate mining and shared-log truncation. Stop can reclaim an instance only when its executable is under this profile's versioned SRBMiner directory and its command uses this slot's exact log path. Windows PID, creation time, executable and command line are rechecked before termination; unrelated instances are not stopped. Unreadable inventory blocks the operation with a diagnostic.

Controlled update shutdown also checks for these survivors, confirms their exit and preserves their resume intent. Scheduled crash recovery survives an update; a newer explicit Stop cancels captured resume intent. No automatic crash-recovery settings, profiles, clocks or antivirus settings change.

Regression tests use fake processes and mocked Windows inventory. Real Windows recovery is recorded separately in the September 29 audit after rollout. SRBMiner remains 3.7.0, Nanominer 3.10.0 and XMRig 6.26.0.

MineMaster 1.4.9

MineMaster 1.4.9

• Update SRBMiner-MULTI from 3.6.7 to 3.7.0 on Windows and Linux x64, with verified archive and runtime-file hashes. Upstream changes include Quantus compatibility/performance work, Pearl improvements and Intel Arc Quantus support. Actual gains depend on hardware and drivers; no performance benchmark is claimed.
• Nanominer 3.10.0 and XMRig 6.26.0 remain the latest official stable releases as checked September 29, 2026.
• Package only current, verified miner runtime files and supplied notices. Exclude obsolete cached versions, optional drivers and unrelated files. Verify the packaged Windows/Linux file lists and hashes before publication.
• Check official latest stable miner releases before publishing a client release. Fail clearly if pins are outdated or upstream assets cannot be verified; do not automatically change binaries.
• Correct Nanominer pool endpoint and reconnect reporting, retaining original observation times.
• Include up to two recent failed managed-file/archive paths in explicit Windows history checks, and show the exact checked paths in admin/client diagnostics. Checks remain read-only and never change protection settings.
• Preserve file inspection failure details through launch preparation and identify config/log/directory write failures separately from executable launch failures.
• Derive admin/client SRBMiner version labels from the shared catalog.
• Correct AMD integrated-GPU inventory and reject placeholder PCI addresses as stable hardware identities.
• Detect parent-process exit before output-handle closure; block duplicate starts, repairs and updater handoff while descendant/process closure remains uncertain.
• Show automatic-install behavior and paused-install errors in the admin/client. A newer Stop cancels update preparation.

Supported clients on 1.4.9 automatically install verified downloads, safely stop mining, restart and resume previously running enabled processes. Failed/canceled attempts require an explicit retry. Older clients require one installation request to adopt this behavior. No forced fleet update, mining action, repair, profile change or antivirus modification is part of this release. Custom executable paths remain operator-managed.

See audit evidence and validation limits.