Silent Mode — releases

Canonical SHA-256 checksums for every published build. This page lives at the on-chain name releases.silentmode.bch; the name pins where it is served from, so a tampered mirror cannot change what you check against here.

Theseus Navigator 0.3.24

Windows 64-bit · unsigned · 2026-09-08 · Slimmer installer + settings light-mode readability — Theseus no longer bundles AriadneResolver-Setup; it fetches from silentmode.st when the user clicks Install in Settings, dropping the installer size by ~24 MB. Settings light mode gets a new --acid-text variable so text (⛓ Theseus brand, active nav, Check-for-updates button, status highlights) renders as BCH dark navy #253A49 — ~12:1 on white, no more marginal green. Brand-green fills / borders / tints still use --acid. Dark mode unchanged.
f24d16a43021cea1b7317ae5e0aa24fe7c9b1264332dfba92b82d1a2057deb67
d5e64ab5e9e038b658692eb9c615f0189c2547f91d96d50044fb0f7dbc39a0d3

Ariadne Resolver — Windows 0.1.1

Windows 64-bit · unsigned · bundled Node runtime · 2026-09-08 · NRPT list from the BNS indexer + install-log-on-disk — TLD discovery now hits silentmode.st/api/tlds over HTTPS (electrum/config kept as fallbacks) so silent installs no longer get stuck when WSS is blocked. install.ps1 writes a persistent transcript at C:\ProgramData\Ariadne\install.log, plus a separate install-error.log on any uncaught exception, and Inno's own log is copied there too — so a /VERYSILENT failure always leaves forensics. Fixes the class of bug where the resolver appeared installed but the BNS Resolver Daemon scheduled task was never registered.
be1fa8841919b321841d90f8147abe1b1d7604fe7fff6c2e271dc47c4c24a2b6

Ariadne for Android 0.11

Android 5.0+ (API 21) · self-signed release key · 2026-08-30 · adds Sia CDN pull to the APK-bundled starter — post-install cold starts now catch up from the operator's latest published snapshot in one HTTP call
03c95832c16cc4763acaadbf328caa7d4bd05fc7c2994f6997a79cc6890bca44
Signing certificate — SHA-256 (the same key signs every future release)
46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c
How to verify. After downloading, compute the file's SHA-256 and compare it to the value above — on Windows: certutil -hashfile <file> SHA256; on Android, hash the downloaded .apk on a computer before you move it to the phone, or use any file-hashing app. Nothing here is signed by an authority your device already trusts — by design — so it will warn about an unrecognized app; the checksum is the real check. The machine-readable manifest is at releases-manifest.json.