The thread that leads out of the DNS maze. Ariadne reads names straight from the Bitcoin Cash chain and answers on the device: no gateway to trust, no operator who can rewrite the answer. It ships three ways: a mobile browser for Android, a standalone system-wide resolver for Windows, and built into every Theseus install.
Ariadne.X is the mobile browser's sovereign site, served from its own on-chain name.
Mirror: silentmode.st/ariadne-x/ ·
gateway: navigate.st/bns/ariadne.x/ ·
native with a resolver: https://ariadne.x/
A phone-sized browser that resolves Bitcoin Cash names on the device. Every lookup asks the on-device snapshot and a live Electrum server in parallel and takes whichever answers first; if they disagree, the chain wins. Sia-hosted pages are fetched from the bucket directly, with no gateway in between. Tap the badge on any page to see the block and transaction behind the name.
Ariadne's Thread is one tap away inside the app: a local VPN service that resolves names for every app on the phone, not just this browser. No root, no profile, nothing installed at OS level. The app updates itself once installed.
da3655262114cd0505b69c9833ea129c2808dc3fbb8c0137abd60bad1595961546ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548cFor anyone who wants names working in every browser on the machine without installing Theseus. It runs as a small background service that answers name lookups and mints TLS certificates on the fly for names registered on chain. The Theseus installer offers the same component as "Ariadne's Thread".
Asks for administrator rights because it changes how the machine resolves names: a
background service, routing rules that send only the chain's TLDs to the local daemon, and
one root certificate name-constrained to those TLDs, so it cannot vouch for
.com. Everything reverses with the bundled uninstaller.
a16d10759efede4412f4fdb52d59424bf56bbb258bb002ab930f4a5a5aef8a41h record is a page
inside a transaction; s3 fetches the Sia bucket directly;
ip connects to a host with its TLS fingerprint pinned on chain;
u redirects.Hash the .apk on a computer before moving it to the phone, or use
any file-hashing app, and compare to the value above. The signing-key fingerprint matters most:
Android refuses any update signed by a different key.
certutil -hashfile <file> SHA256. The build carries no
code-signing certificate, so Windows warns about an unrecognized app. That warning is
expected; the hash is the check.
The releases page lists current builds with checksums, and the machine-readable manifest is what the apps themselves update from.