A Chromium-based browser with native .bch / BCNR name resolution built in.
No OS-level daemon, no DNS shim, no root-store install. Type hello.bch in the
address bar and it just works.
Windows builds for now. The installer wires shortcuts and file associations; the portable build is a single .exe that runs from anywhere. Ariadne Resolver is the older, lighter option for systems where you only need name resolution without the browser.
Installs with shortcuts + Start menu entry. Recommended for most users.
Single .exe. Nothing installed, nothing modified in the registry. Run and go.
The lighter option: a system-wide BCNR resolver (no browser). Works with any browser via the local trust anchor. Windows installer.
Android APK. Runs as a VPN service to intercept and resolve BCNR names on the device.
Theseus is a Chromium wrapper (Electron) with two things regular browsers don't have: in-process BCNR name resolution, and a certificate-verify hook that trusts on-chain TLS fingerprints instead of the OS root store for BCNR hostnames.
.bch / .x / any BCNR TLD.
The URL parser is short-circuited: any hostname whose TLD is in the registry is
resolved by walking the chain via the built-in bns.js — never through DNS.h renders inline HTML from the OP_RETURN payload itself. s3
serves from a Sia bucket via the in-app gateway. ip connects to a server by
IP. u redirects. Priority is handled by the shared record-picker.setCertificateVerifyProc is intercepted: for BCNR hostnames,
instead of walking the OS trust chain, the leaf's SHA-256 fingerprint is compared to the
tls record on chain. Matches → trusted. No tls record → the
browser falls back to the local root CA.The binaries are unsigned (Windows will show a SmartScreen warning). Before running, verify the SHA-256 against what the operator publishes on-chain and in the release notes:
PowerShell: Get-FileHash TheseusNavigator-Setup-0.0.4.exe Bash: sha256sum TheseusNavigator-Setup-0.0.4.exe
Compare the digest to the release manifest at
silentmode.st/releases/.
For a stronger guarantee, sign in with the wallet and check that the release-signing key
matches the on-chain identity for releases.silentmode.bch.