Skip to content

Updating Sthang

Sthang uses one Stable channel and one fixed private in-app update service.

The current Stable baseline is 1.0.0. It is delivered only to an enrolled, licensed Sthang installation; the update service is not an anonymous download page.

How updates work

  • Sthang checks once after startup completes. The check does not delay the license gate or main window.
  • You can choose About / Updates → Check for updates at any time.
  • On first use, the licensed device privately enrolls for a separate revocable OTA access credential. No GitHub account is required.
  • Sthang displays the available version and sanitized plain-text release notes.
  • Nothing is downloaded automatically.
  • You must confirm the displayed version and choose Download and update.
  • The downloaded installer must pass the embedded Tauri updater signature check before installation.

Before you begin

Stop minting, transfers, Sweep, signing, broadcasts, and wallet-authenticated scans. Sthang will not interrupt active financial work; it reports busy until that work reaches a clear final state.

Confirm that the available version is the version you expect and read the displayed release notes. Create a current backup before a major operational change.

Download and install

Choose Download and update only after Sthang is idle. Keep the application open while it downloads and validates the artifact. The application installs only after its embedded updater key accepts the signature.

If a download, signature, manifest, or install step fails, Sthang stays on the current version, releases its temporary hold, and waits for an explicit later retry. It does not poll repeatedly or switch servers.

If private update access expires or is revoked, use Check for updates again. Sthang will attempt to refresh access only while the installed device-bound license remains valid. The OTA credential is Windows-user protected and is never displayed in the interface.

Your license and per-user application data remain in their stable data locations during a normal upgrade.

Expected result

Sthang relaunches on the displayed Stable version. Your existing activation, configuration, shared UI state, wallet-folder references, attempt history, and duplicate-prevention records remain available.

Stop and get help

Stop if the available version is unexpected, validation fails, the application remains busy after work reaches a clear final state, or activation or configuration is missing after relaunch. Do not fetch a replacement installer or update description elsewhere. Keep live work stopped and use the private support channel.

User documentation for privately distributed Sthang installations.