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.26
Windows 64-bit · unsigned · 2026-09-08 · Screenshot no longer blank + editor Discard button + manual add-on update controls — Three fixes since 0.3.25. (1) Screenshot toolbar-menu captures no longer come out blank on Windows: the capture path moves from WebContents.capturePage() (which was snapshotting a stale/transparent frame when the tab view was still marked occluded after the native menu popup closed — a size-based retry couldn't catch that) to CDP Page.captureScreenshot, which forces a fresh composite regardless of occlusion state. (2) Editor grows a Discard button (and top-level Escape) that closes the editor tab and drops the working screenshot — no more stuck editor when capture came out unusable. (3) Settings > Extensions grows a Check for updates button and a Pending updates surface — the signed add-on update endpoint is now controllable by hand from the UI, not only on the boot timer. Everything from 0.3.22 – 0.3.25 rides along.
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.
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
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.