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.59
Windows 64-bit · unsigned · 2026-09-28 · 0.3.59 — DNS over HTTPS, Global Privacy Control, Settings pages with addresses — Privacy, regrouped: Settings › Privacy now opens with a status card and gathers tracking protection (Shield and Cookie Pop-ups with their per-site exceptions), device access, anti-fingerprinting, network and browsing data in one place. New there: DNS over HTTPS (on by default with Quad9; Cloudflare, Mullvad, AdGuard or your own resolver; an increased-protection mode that never falls back to plain DNS) and Global Privacy Control, which tells every site not to sell or share your data (the Sec-GPC header plus navigator.globalPrivacyControl). Every Settings page has an address you can copy and open, theseus://settings/privacy for example, with sub-pages for the longer lists. Search-engine icons ship inside Theseus and a custom engine's icon is cached once, so the toolbar, the picker and Settings look the same offline and opening the picker no longer asks a favicon service which engines you use; the default-engine control in Settings shows the icons too. A video's fullscreen now hides the toolbar and leaving it, switching tabs or closing the tab puts the window back (before, the window could stay fullscreen with no title-bar buttons); F11 toggles fullscreen. A name owner's subdomain rules (a blocked or redirected subdomain) now apply in Theseus for names it reaches directly by IP as well, not only through the gateway.
Windows 64-bit · unsigned · bundled Node runtime · 2026-09-28 · 0.1.8 — pinned-origin proxy for `ip`+`tls` names — BNS names that publish an ip record with an on-chain tls fingerprint pin (game.x, hephaestus.x, and any other site that pins its origin cert) now load cleanly in every browser. Before 0.1.8 the daemon returned the raw ip and browsers hit the origin directly; if that origin's cert was not browser-trusted (which is the whole point of publishing an on-chain pin) users got ERR_CERT_AUTHORITY_INVALID / SEC_ERROR_UNKNOWN_ISSUER. 0.1.8 answers DNS with 127.0.0.1 whenever ip+tls are both present, terminates the browser's TLS with a locally-trusted leaf, and reverse-proxies to the origin over HTTPS while validating the origin's SHA-256 fingerprint against the on-chain pin — same algorithm Theseus uses in pinnedHttpsGet. Names with just ip (no pin) keep direct routing unchanged, so nothing regresses. Includes 0.1.7 (runtime-switchable collision policy) and 0.1.6 (self-syncing routing + CA). Upgrades in place.
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.
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.