CatStack 1.9.1

General improvements and fixes.

CatStack Remote Connector 0.2.0 beta — guided sign-in

CatStack Remote Connector 0.2.0 beta

Open the downloaded connector, sign in in your browser, confirm the matching
code, and connect your controller. No manual config file or copied token is
required. Downloads and instructions: https://remote.catstack.sh/downloads

• Meowcoin-branded local setup checks that CatStack is running first.
• Browser sign-in preserves optional 2FA and returns to connection approval.
• Connection details are saved privately; passwords stay on CatStack Remote.
• Windows offers automatic startup at sign-in and prevents duplicate instances.
• Headless Linux prints a sign-in link usable from another device.
• Existing --config installations keep working; the complete-response fix is
  included. One controller per account remains the beta limit.
• Device approval expires after ten minutes, requires an authenticated
  same-origin confirmation, and stores only hashed device/connector secrets.

Windows 10/11 x64; Linux x86_64 glibc 2.36+. Keep CatStack running. Linux startup
services are not installed by this release. Windows executables are unsigned;
checksums and the complete source ZIP are included.

Verified with 16 integration tests and both packaged binaries against
disposable controllers through the public gateway. Windows browser sign-in,
matching-code approval, private save, startup installation, duplicate launch,
and restart from the installed copy passed. Linux headless pairing, private
permissions, connection, and duplicate launch passed. Existing operator
credentials were preserved; no real mining or reboot commands were used.

CatStack Remote Connector 0.1.0 beta

CatStack Remote Connector 0.1.0 beta

• Windows x64 and Linux x86_64 standalone connectors for each tester's own
  CatStack controller.
• Outbound WebSocket transport for the dashboard's HTTP controls, live status,
  and SSH terminal.
• Per-account connector tokens are stored as hashes on the gateway and can be
  rotated. Browser sign-in works with a password. Optional 2FA can be enabled
  in Account settings using a locally generated QR code or manual setup key.
• The controller remains the sole owner of rig data. No rig agent, database,
  wallet, or flight sheet migration is performed.
• The connector source and SHA-256 checksums are included with the binaries.
• Corrected response streaming so large dashboard JavaScript files arrive in
  full. Redownload the connector if the dashboard was blank or showed syntax
  errors. The Windows connector now hides its own console window.
• Controller and MeowOS images, checksums, and installation instructions:
  https://remote.catstack.sh/downloads

Initial verification: six local gateway/connector tests passed; both packaged
executables launched with --help; public HTTPS downloads matched SHA-256;
and one mock-controller session passed signup, MFA, rig-list relay, a mock
control POST, and live WebSocket traffic. The mock account was removed. No
production rig command or independent security audit was performed. Broader
hardware compatibility remains unverified.

Update verification: all 11 local integration tests passed, including a large
multi-chunk controller asset. The operator's existing controller connected and
showed all 53 configured rigs with live telemetry and working remote Refresh.
No mining, reboot, or rental settings were changed.

CatStack 2.0.2 RC3 - listed idle undervolting

CatStack 2.0.2 RC3

RC3 enables undervolting during idle mining while Vast listings remain active. Enable idle undervolting verifies ownership and installs a synchronous rental-start guard. The guard restores and reads back the original 0 mV core-voltage demand before Docker starts customer code. It prevents concurrent negative writes, retains the saved idle setting during the rental and automatically resumes it after customer containers are removed and idle mining is stable again. Listings, prices and contracts are not changed. This mode supports Docker rentals; VM-enabled hosts require their own startup integration. Native Windows GPU voltage control is unchanged.

Guard setup uses live reload where supported. If a Docker restart is needed to activate the authorization plugin, setup first enables live restore and verifies that existing containers retain their process IDs. The prior live-restore setting is restored afterward. Keep CatStack running for owner verification and automatic idle resumption; verification loss restores zero.

Core-voltage tuning and the voltage-field keyboard-focus fix follow the existing 2.0.1 RC3 release. Application VERSION is 2.0.2 and the prerelease identity is 2.0.2-rc3.

• Core-voltage demand offset from -300 to 0 mV in 5 mV steps, with global and per-GPU settings, saved profiles and CLI support.
• GeForce RTX 40- and 50-series model eligibility, including Ti, SUPER, D and laptop variants. Actual availability still requires an inspected matching NVIDIA Linux driver/API library, the correct generation layout and verified control readback. The Windows manager controls supported Linux rigs; native Windows GPU core-voltage control remains unavailable.
• Fifteen-minute probation, continued monitoring, independent systemd recovery and rental-host protections. Existing profiles do not automatically opt in. Zero restores the original demand.
• Live fleet updates preserve focus while entering a negative voltage value. Per-GPU input boxes are wider and their table scrolls within its panel.
• Retains 2.0.1 RC3's Push SSH Key retry and authentication messages, current-run OC error reporting, headless NVML offsets, native NVIDIA memory/hotspot temperatures, current SSH miner output, and automatic-update/discovery repair with customer-workload deferral.
• Retains AMD support and the 45-day unused-flight-sheet retention introduced in the later beta snapshots.

Qualification is specific to the card, clock and workload. The full manual offset range has not been qualified for stability. Deep RTX 5070 Ti trials at -100/-125 mV caused firmware hangs requiring recovery; software rollback cannot guarantee restoration after a firmware hang. Measured power comparisons used NVIDIA board-power telemetry and miner hashrate, rather than wall-meter energy.

Extract the manager archive to a new folder and use the existing farm-data directory. Verify the archive against its SHA-256 sidecar. No new MeowOS disk image is included and no rig reflash is required.

Live RC3 validation on a listed RTX 5070 Ti verified -5 mV, restoration to 0 mV before a controlled GPU container's first command, and automatic resumption to -5 mV after that container was removed. The test finished at 0 mV. Listing status and all recorded offer terms were unchanged; no paid rental was created. Focused tests cover startup/write serialization, failure to restore, Docker message casing, deleted-container holds, profile preservation and listing-preserving ownership checks. Desktop/mobile browser tests cover the new controls and uninterrupted typing.

Regression validation: 641 Windows tests passed with 11 Linux-runtime checks skipped; all 652 Linux tests passed. Twelve rendered desktop/mobile checks passed. Windows and Linux managers retain the 2.0.1 fixes and include compiled worker 0.4.27 plus the inspected voltage/admission helpers.

Build source snapshot (private): 5ee1859fa6cfe6c9806c941a9f38d0610d2faba9. Both manager packages include compiled Linux worker 0.4.27; application source is not published. Packaged CLI/profile and HTTP API identity checks passed on Windows and Linux, and the Windows sensor passed its self-test.

CatStack 2.0.2 RC2 - Linux owner voltage controls

CatStack 2.0.2 RC2

RC2 fixes core voltage remaining unavailable on Linux RTX 40/50 Vast owner rigs because the manager previously required a temporary qualification file. The Tuning panel now offers Pause Vast listing & enable core voltage, which verifies ownership and zero allocations, pauses the idle offer and enables the field. CatStack renews the normal owner authorization while running. The supervisor restores zero if verification expires or rental/listing state changes. Restore core voltage & end tuning ends the session; the listing stays paused until the owner resumes it in Vast. This update does not add native Windows GPU voltage control.

Core-voltage tuning and the voltage-field keyboard-focus fix follow the existing 2.0.1 RC3 release. Application VERSION is 2.0.2 and the prerelease identity is 2.0.2-rc2.

• Core-voltage demand offset from -300 to 0 mV in 5 mV steps, with global and per-GPU settings, saved profiles and CLI support.
• GeForce RTX 40- and 50-series model eligibility, including Ti, SUPER, D and laptop variants. Actual availability still requires an inspected matching NVIDIA Linux driver/API library, the correct generation layout and verified control readback. The Windows manager controls supported Linux rigs; native Windows GPU core-voltage control remains unavailable.
• Fifteen-minute probation, continued monitoring, independent systemd recovery and rental-host protections. Existing profiles do not automatically opt in. Zero restores the original demand.
• Live fleet updates preserve focus while entering a negative voltage value. Per-GPU input boxes are wider and their table scrolls within its panel.
• Retains 2.0.1 RC3's Push SSH Key retry and authentication messages, current-run OC error reporting, headless NVML offsets, native NVIDIA memory/hotspot temperatures, current SSH miner output, and automatic-update/discovery repair with customer-workload deferral.
• Retains AMD support and the 45-day unused-flight-sheet retention introduced in the later beta snapshots.

Qualification is specific to the card, clock and workload. The full manual offset range has not been qualified for stability. Deep RTX 5070 Ti trials at -100/-125 mV caused firmware hangs requiring recovery; software rollback cannot guarantee restoration after a firmware hang. Measured power comparisons used NVIDIA board-power telemetry and miner hashrate, rather than wall-meter energy.

Extract the manager archive to a new folder and use the existing farm-data directory. Verify the archive against its SHA-256 sidecar. No new MeowOS disk image is included and no rig reflash is required.

RC2 validation: 619 Windows tests passed with 11 Linux-runtime checks skipped; all 630 Linux tests passed. Twelve rendered desktop/mobile checks cover owner preparation/reset and uninterrupted voltage entry. A live RTX 5080 on NVIDIA 595.91.07 completed normal owner preparation, applied and read back -5 mV, and independently restored 0 mV when manager renewal stopped. The original Vast offer and terms were restored. This verifies the normal product path, not only the model-name eligibility check.

Build source snapshot (private): 5fbd4c10784ad4fb4430ba1cf65f21a2b292d466. Both manager packages include compiled Linux worker 0.4.27; application source is not published. Packaged CLI/profile and HTTP API identity checks passed on Windows and Linux, and the Windows sensor passed its self-test.

CatStack 2.0.2 RC1 - core voltage control and tuning fixes

CatStack 2.0.2 RC1

Core-voltage tuning and the voltage-field keyboard-focus fix follow the existing 2.0.1 RC3 release. Application VERSION is 2.0.2 and the prerelease identity is 2.0.2-rc1.

• Core-voltage demand offset from -300 to 0 mV in 5 mV steps, with global and per-GPU settings, saved profiles and CLI support.
• GeForce RTX 40- and 50-series model eligibility, including Ti, SUPER, D and laptop variants. Actual availability still requires an inspected matching NVIDIA Linux driver/API library, the correct generation layout and verified control readback. The Windows manager controls supported Linux rigs; native Windows GPU core-voltage control remains unavailable.
• Fifteen-minute probation, continued monitoring, independent systemd recovery and rental-host protections. Existing profiles do not automatically opt in. Zero restores the original demand.
• Live fleet updates preserve focus while entering a negative voltage value. Per-GPU input boxes are wider and their table scrolls within its panel.
• Retains 2.0.1 RC3's Push SSH Key retry and authentication messages, current-run OC error reporting, headless NVML offsets, native NVIDIA memory/hotspot temperatures, current SSH miner output, and automatic-update/discovery repair with customer-workload deferral.
• Retains AMD support and the 45-day unused-flight-sheet retention introduced in the later beta snapshots.

Qualification is specific to the card, clock and workload. The full manual offset range has not been qualified for stability. Deep RTX 5070 Ti trials at -100/-125 mV caused firmware hangs requiring recovery; software rollback cannot guarantee restoration after a firmware hang. Measured power comparisons used NVIDIA board-power telemetry and miner hashrate, rather than wall-meter energy.

Extract the manager archive to a new folder and use the existing farm-data directory. Verify the archive against its SHA-256 sidecar. No new MeowOS disk image is included and no rig reflash is required.

Validation: 600 Windows tests passed with 11 Linux-runtime checks skipped; all 611 Linux tests passed. Sixteen rendered desktop/mobile checks cover voltage entry during live updates, keyboard focus, input range and separate GPU temperatures. A release-identity regression verifies that the manager advances beyond 2.0.1 and that its reported version and prerelease label agree.

Build source snapshot (private): 0229ff25c9e989afa6284614bc4e7b50fa003334. Both manager packages include compiled Linux worker 0.4.27; application source is not published. Packaged CLI/profile and HTTP API identity checks passed on Windows and Linux, and the Windows sensor passed its self-test.

CatStack 2.0.1 RC3 - Push SSH Key fix

CatStack 2.0.1 RC3

CatStack 2.0.1 adds native Linux GPU memory and hotspot monitoring, fixes stale SSH miner output, and repairs an older deployment policy that could leave rig updates disabled after a manager upgrade.

RC3: Push SSH Key fix

Push SSH Key could fail when adding a rig, with an error claiming the default MeowOS password was wrong. The password had not changed. CatStack turns off SSH password login after its first successful key push, so any later click on that rig failed on the password step, even though CatStack's key was already installed.

• Push SSH Key now reuses CatStack's key when the rig already accepts it and reruns rig setup, instead of trying the default password.
• When a rig has SSH password login turned off and does not have this CatStack's key, the error says so and shows how to re-enable it from the rig's console. It no longer blames a custom image.
• If the key is installed but rig setup fails, the message says the key works and points to Recover Agent.
• GPU overclock Apply failures show only the latest run's errors. Large rig OC logs with corrupted bytes previously produced months-old Xorg errors.

Changes retained from RC2 and RC1

• Apply NVIDIA core and memory offsets through native NVML on headless Linux rigs, identified by GPU UUID and verified by readback. Unsupported drivers keep the Xorg fallback.
• Read GPU memory and hotspot temperatures directly on supported Linux GPUs and drivers.
• Follow the current miner and its live output when connecting over SSH, including after miner changes and log rotation.
• Enable update and discovery services during deployment, including on Vast hosts, and persist the working manager address across reboots.
• Keep update timers enabled during rentals. Updates that would restart services wait while customer or unidentified workloads are present and retry automatically.
• Report failures to enable automatic updates, and show the current reported agent version.

Updating

1. Download the Windows ZIP or Linux archive and verify it against the adjacent SHA-256 file.
2. Back up your farm data, close the old manager and extract this application into a separate folder.
3. Start CatStack 2.0.1 RC3.

No rig reflash is needed. MeowOS 1.8.6 rigs keep the same default login.

Validation

• Linux: 483 tests passed.
• Windows: 471 tests passed; twelve Linux-only tests skipped.
• New tests cover Push SSH Key on a rig that already has CatStack's key, on a fresh rig, and on a rig with password login turned off.
• Both packages passed checksum, manifest and source-identity verification, and the packaged CLIs, Windows sensor and all four Linux worker components passed launch/self-tests.
• The fix was confirmed inside both packaged builds.

This is a manager prerelease with the compiled Linux rig worker. It does not include a newly built MeowOS disk image.

Build source commit: afd0fad1ed7782a1585f439d4be9a30941b5ae87.

CatStack 2.0.1 RC2 - headless GPU overclock fix

CatStack 2.0.1 RC2

CatStack 2.0.1 adds native Linux GPU memory and hotspot monitoring, fixes stale SSH miner output, and repairs an older deployment policy that could leave rig updates disabled after a manager upgrade.

RC2: headless GPU overclock repair

Fix GPU overclock Apply failures on Linux rigs where the NVIDIA driver works but Xorg has no usable control display. Core and memory offsets now use native NVML, identify the GPU by UUID, check supported ranges, and verify the applied values. Unsupported drivers retain the Xorg fallback. Permission errors and failed readback remain visible failures.

Clock-lock resets run before offsets are applied, preserving the requested unlocked-memory setting. Positive core locks and memory-lock precedence are retained.

The generated persistent script was verified on an RTX 5070 Ti with driver 580.178.04: +150 core, +3000 memory, a 2640 MHz core target, unlocked memory and a 275 W limit. GPU and CPU miners resumed with fresh accepted shares.

Changes retained from RC1

• Read GPU memory and hotspot temperatures directly on supported Linux GPUs and drivers. Windows is not required for Linux rig readings. Unsupported sensors remain unavailable instead of showing invented or stale temperatures.
• Follow the current miner and its live output when connecting over SSH, including after miner changes and log rotation.
• Enable update and discovery services during deployment, including on Vast hosts, and persist the working manager address across reboots.
• Keep update timers enabled during rentals. Updates that would restart services wait while customer or unidentified workloads are present and retry automatically.
• Include the update guard in desktop packages, manual deployment, agent bundles and the image build path.
• Report failures to enable automatic updates, and show the current reported agent version.

Updating

1. Download the Windows ZIP or Linux archive and verify it against the adjacent SHA-256 file.
2. Back up your farm data, close the old manager and extract this application into a separate folder.
3. Start CatStack 2.0.1. Rigs with enabled automatic updates receive the newer bundle from the manager.

An updater that was previously disabled on an existing rig must be enabled once; changing the manager alone cannot start a disabled remote timer. Rigs also need a working manager address and sufficient free storage. Customer-workload deferrals leave the timer enabled.

Validation

• Linux: 480 tests passed.
• Windows: 468 tests passed; twelve Linux-only tests skipped.
• Both packages passed checksum, manifest, source-identity and bundled-update-guard verification.
• Both packaged CLIs, the Windows sensor and all four Linux worker components passed isolated launch/self-tests.
• Native Linux memory and hotspot monitoring is retained from RC1; the worker source is unchanged.

This is a manager prerelease with the compiled Linux rig worker. It does not include a newly built MeowOS disk image.

Build source commit: 3fd70d5de8bbac1ff2e1e36f7380302d8cfd0cc2.

CatStack 2.0.1 RC1

CatStack 2.0.1

CatStack 2.0.1 adds native Linux GPU memory and hotspot monitoring, fixes stale SSH miner output, and repairs an older deployment policy that could leave rig updates disabled after a manager upgrade.

Changes

• Read GPU memory and hotspot temperatures directly on supported Linux GPUs and drivers. Windows is not required for Linux rig readings. Unsupported sensors remain unavailable instead of showing invented or stale temperatures.
• Follow the current miner and its live output when connecting over SSH, including after miner changes and log rotation.
• Enable update and discovery services during deployment, including on Vast hosts, and persist the working manager address across reboots.
• Keep update timers enabled during rentals. Updates that would restart services wait while customer or unidentified workloads are present and retry automatically.
• Include the update guard in desktop packages, manual deployment, agent bundles and the image build path.
• Report failures to enable automatic updates, and show the current reported agent version.

Updating

1. Download the Windows ZIP or Linux archive and verify it against the adjacent SHA-256 file.
2. Back up your farm data, close the old manager and extract this application into a separate folder.
3. Start CatStack 2.0.1. Rigs with enabled automatic updates receive the newer bundle from the manager.

An updater that was previously disabled on an existing rig must be enabled once; changing the manager alone cannot start a disabled remote timer. Rigs also need a working manager address and sufficient free storage. Customer-workload deferrals leave the timer enabled.

Validation

• Linux: 460 tests passed.
• Windows: 452 tests passed; eight Linux-only tests skipped.
• Both packages passed checksum, manifest, source-identity and bundled-update-guard verification.
• Both packaged CLIs, the Windows sensor and all four Linux worker components passed isolated launch/self-tests.
• The exact compiled worker returned native memory and hotspot readings on RTX 4070 Ti SUPER and RTX 5070 Ti Linux rigs.

This is a manager prerelease with the compiled Linux rig worker. It does not include a newly built MeowOS disk image.

Build source commit: 445d6430f7adce518ba3832ac9e34e5beb5aa3b4.

CatStack 2.0 Beta 2 - 45-day flight-sheet cleanup

CatStack 2.0 Beta 2 — automatic flight-sheet cleanup

CatStack now records the last time a flight sheet is applied through the
dashboard, CLI, or Pearl preset command. Once per day, it removes a sheet only
if it has not been applied for more than 45 days and is not assigned to any
rig's GPU or CPU slot. New sheets never applied expire 45 days after creation.

Existing databases have no historical last-applied timestamps. The migration
gives those sheets a 45-day grace period instead of guessing from their edit
dates. Deletions are logged by name. The cleanup changes only CatStack's
flight-sheet records; it does not contact or restart rigs.

This manager update retains the AMD GPU support from Beta 1. The matching
MeowOS Beta 1 image is available from the CatStack CDN and the
Beta 1 release.
AMD mining on a particular card still requires a compatible flight sheet and
a fresh accepted-share check.

Windows and Linux bundles include compiled worker 0.4.26. No worker Python
source is included. The private source snapshot SHA-256 is
d6a184146d005e8533118ee1069582a1882132fc297dd84b4a0e5ace48b445b5;
the local source worktree has no connected Git commit.