diff --git a/GOTCHAS.md b/GOTCHAS.md index 4168250..d407db1 100644 --- a/GOTCHAS.md +++ b/GOTCHAS.md @@ -39,12 +39,29 @@ release blocks are generated from it. After adding a release to the manifest: node scripts/releases-page.mjs # trims the manifest, rewrites the blocks ``` -then scp `releases/index.html` + the manifest (both VPS paths). Do not hand- -edit the blocks; the next run overwrites them. Consumers (Theseus + Ariadne -updaters, `dl-latest.sh`) read only the first entry per product id, so +then scp `releases/index.html` + the manifest (both VPS paths) + the +generated `releases/dl-index.html` → `/opt/silent-mode/dl/index.html` (the +dl host has no shared.css, so that copy uses absolute links). Do not hand- +edit the blocks; the next run overwrites them. Consumers (Theseus + Ariadne + +Hermes updaters, `dl-latest.sh`) read only the first entry per product id, so trimming never changes what they see. Older builds live on Sia under `dl-archive/` and every old checksum is in git history. +**Ship to dl FROM the repo manifest, never the other way round.** On +2026-10-24 a session wrote its product's entries straight into +`/opt/silent-mode/dl/releases-manifest.json` from a stale base and silently +dropped four newer Theseus and two Ariadne entries — the auto-updater served +0.3.106 while 0.3.110 was on the host. Merge into `site/releases-manifest.json` +first (union by id+version+platform), run the script, then scp. + +**Prune the VPS with `scripts/dl-vps-archive.sh`** (all products, `--dry-run` +first). Its keep table must match `KEEP` in `releases-page.mjs`, or the page +links installers the host no longer has. `/latest/` redirects are generated on +the VPS by `/opt/silent-mode/bin/dl-latest.sh` (cron, 5 min), tracked at +`VPS/SilentMode/dl-latest.sh`; a new product needs a row there too. + +**Check links after editing pages:** `node scripts/site-linkcheck.mjs`. + ## Old Theseus builds fill the VPS disk `scripts/theseus-vps-archive.sh ` moves everything older than N-1 to diff --git a/ariadne/index.html b/ariadne/index.html new file mode 100644 index 0000000..7de008c --- /dev/null +++ b/ariadne/index.html @@ -0,0 +1,172 @@ + + + + + +Ariadne — the resolver and the mobile browser — Silent Mode + + + + + + + + + + + + + + + + + + +
+
+

Ariadne resolver

+

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.

+
+ Android browser + Windows resolver + How a lookup resolves +
+

+ 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/ +

+
+ +
+ +
+ Ariadne for Android showing silentmode.bch resolved on the phone, with the BCN badge in the address bar +
silentmode.bch opened in Ariadne for Android. The badge says the name came from the chain.
+
+ + +
+

Ariadne for Android

+

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.

+
+
+ alpha +

Ariadne for Android 0.52

+

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.

+
Android 5.0+ (API 21) · self-signed release key · 2026-10-24
+
SHA-256 da3655262114cd0505b69c9833ea129c2808dc3fbb8c0137abd60bad15959615
+
Signing key 46ebbbe5dc73148d66410fd0337b1e6683472128c983e8e2578200b9e3ca548c
+
+
+ Download APK + ariadne.x +
+
+
+ + +
+

Ariadne Resolver for Windows

+

For 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".

+
+
+ alpha +

Ariadne Resolver 0.1.13

+

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.

+
Windows 64-bit · bundled Node runtime · unsigned · 2026-10-01
+
SHA-256 a16d10759efede4412f4fdb52d59424bf56bbb258bb002ab930f4a5a5aef8a41
+
+
+ Installer +
+
+
Inside Theseus. The desktop browser carries the same resolver + in-process, so it needs none of this. The installer's optional "Ariadne's Thread" step installs + this standalone resolver alongside, for Chrome, Edge and everything else on the machine.
+
+ + +
+

How a lookup resolves

+
    +
  1. Type a name.Anything with a dot goes to the resolver; a bare word is a search. + The name is normalised to its registered form first.
    2. +
  2. Two sources, first answer wins.The bundled on-device snapshot and a live Electrum + server are asked in parallel. If they disagree, the chain's answer is used. Nothing blocks + the navigation.
    3. +
  3. Read the record, serve the page.An h 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.
    4. +
  4. Show the proof.The badge in the address bar names the registry and the storage + that served the bytes. Tap it for the block height and transaction.
    5. +
+
+ + +
+

Verify what you downloaded

+
+
+

Android

+

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.

+
+
+

Windows

+

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.

+
+
+

Every build, every hash

+

The releases page lists current builds with checksums, and the + machine-readable manifest is + what the apps themselves update from.

+
+
+
+ +
+ + + + + diff --git a/bergamot/index.html b/bergamot/index.html index a2e9e95..5b9e4d4 100644 --- a/bergamot/index.html +++ b/bergamot/index.html @@ -34,14 +34,15 @@
diff --git a/brand/index.html b/brand/index.html index 3f96bd9..740e21b 100644 --- a/brand/index.html +++ b/brand/index.html @@ -50,6 +50,7 @@