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.48
Windows 64-bit · unsigned · 2026-09-15 · 0.3.48 — HTTP sign-in prompt, local files from the address bar — Sites behind HTTP authentication (Basic/Digest, e.g. an admin dashboard behind a realm) now get a sign-in prompt instead of the server's bare 401 page; Cancel leaves the 401, a rejected password asks again, and add-on proxy credentials keep their own path. Typing or pasting a local path (D:\folder\page.html, a UNC share, or a file:// URL) opens the file instead of sending it to the search engine; local-file tabs keep their file:// address, show a “Local file” badge, and a missing file lands on the error page. Includes everything from 0.3.47 (Plug-ins section, in-panel add-on self-update, Aegis 0.6.31) and 0.3.46 (updater self-heal, BCNR fetch error page).
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.
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.
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.