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

Windows 64-bit · unsigned · 2026-09-22 · 0.3.52 — one-click extension installs, plug-in row, Word editor in the box — Extensions: install straight from theseus.x/extensions — the page hands Theseus a catalog id, Theseus fetches the package itself, asks in a native dialog, verifies the publisher's signature against the name's current owner in its own chain index, and activates it; theseus://extensions/install/<id> links do the same from any page or the address bar. The page gained a search field and lists every bundled add-on. Layout: Aegis and the Tor switch moved to a plug-in row under the Theseus menu, always visible and never folded into the extensions overflow; the toolbar keeps the extension buttons. Add-ons: Word editor ships in the box with its own signed update channel (Save as…, PDF export); PDF Editor marks stay editable after you place them; Translate fetches from the add-on side so it works on every page; a VPN add-on (preview, sing-box under our own UI) is bundled. Also, from 0.3.50 and 0.3.51: the tab strip scrolls Firefox-style with arrows instead of running under the window buttons, the home page carries the Theseus icon, one Extensions list in Settings, and the profile now lives at %APPDATA%\Theseus with add-ons under extensions\ — migrated from either old folder name on first start.
2c0d1795d73bfb7557b090b77cfedefe6b7945ef580b028853e8afcb3984e5cc
be899b9707cd888f2e86b5406262edac10143fec0ebb23656180501517617734

Ariadne Resolver — Windows 0.1.3

Windows 64-bit · unsigned · bundled Node runtime · 2026-09-19 · Same rules as every other client — Resolver library brought level with the desktop reader: per-TLD certificate registry read from the TLD beacon, current NFT owner tracked per name, the port-443 electrum route tried first, and the TLD co-sign rule (a registration under a "cosign" or hidden TLD is only recognised when it carries the TLD's certificate). Same daemon, same install; existing installs upgrade in place.
79b920b8e4e92aa9a54653035a4873dd996b5d4a9093c43d114e0a3ee4ffb003

Ariadne for Android 0.19

Android 5.0+ (API 21) · self-signed release key · 2026-09-19 · 0.19 — co-sign rule — Consensus fix: the on-device index now applies the TLD co-sign rule. A name registered under a TLD whose owner set policy "cosign" or switched the TLD off (hidden) only counts when the registration transaction also carries the TLD's own certificate, exactly as the gateway, Theseus and the desktop resolver decide it, so every client agrees on which names exist. The index reads the per-TLD certificate registry and its policy history from the TLD beacon at build time; if that beacon cannot be reached it keeps the previous behaviour instead of returning an empty index. No UI changes.
d2f4ad359e7ac36c1d0729100aef613be968cd17b153e94e124f8500fcbfc711
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.