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.65

Windows 64-bit · unsigned · 2026-10-02 · 0.3.65 — Updates panel can't silently fatal into "Loading…" any more — Settings › General › Updates used to stay on "Loading…" forever if anything earlier in the shared Settings init threw, or if the version IPC rejected — the .catch(()=>{}) on the version fetch swallowed it, so Check for Updates became unclickable. The panel init now wraps in its own try, surfaces the actual error on the status line, and keeps Check for Updates functional either way. The toolbar's auto-update chip was always unaffected — it runs independently.
a72ad76a86499e41d18a3e4f911a83415853b0ac3be27782f137bd25ad0666c6
f627d7cf33dbc3cb21a6ce85308420e43443695eac5c5364d61bc99e811add4e

Ariadne Resolver — Windows 0.1.13

Windows 64-bit · unsigned · bundled Node runtime · 2026-10-01 · 0.1.13 — every subsystem is switchable and reports its own state — New endpoint http://127.0.0.1/api/status returns a full state report: daemon version + startup + policy + permitted TLDs + ports + upstream + gateway; index size + warm-start source; and per-source enabled/lastAttempt/lastSuccess/lastError/counters for snapshotHttps, electrumWss, perQueryLookup, diskCache, localApi. Same JSON drives a settings UI (once Theseus's Plug-ins panel picks it up) and is a support-ready "current state" dump. C:\ProgramData\Ariadne\policy.json extended with a sources.<name>.enabled block (hot-reloaded every 5 s alongside the collision policy) — flip any source off to isolate a path or measure without it. Includes 0.1.12 (orphan-safe upgrade + local BNS indexer API). Upgrades in place.
a16d10759efede4412f4fdb52d59424bf56bbb258bb002ab930f4a5a5aef8a41

Ariadne for Android 0.20

Android 5.0+ (API 21) · self-signed release key · 2026-09-28 · 0.20 — every live TLD, fresh snapshot — Every live BNS TLD is claimed by the on-device resolver. The app took its TLD list from the registry's legacy advertised set (nine TLDs), so a name under a newer TLD was only intercepted once it had turned up in the local index; the app now reads the registry's routable list (every TLD on the public listing, 24 today), and ships a bootstrap list matching it for cold start. The cold-start snapshot it pulls from the CDN is now refreshed every ten minutes from the gateway's index instead of by hand, so a fresh install sees names registered minutes ago rather than weeks. Same signing key; installs over 0.19.
e7362e356de14f010646f3c60908ccd4bbd8030914f7e6a5dc2722d9dcf5e51e
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.