Theseus Navigator — Silent Mode's Electron browser with the Ariadne resolver built in.
95d199c2f2
An end-to-end drive of the update flow against a local HTTP server hit two Windows-only tar quirks that a first-cut MVP wouldn't catch: 1. Git-Bash tar (MSYS2), which comes first on PATH when Git-for-Windows is installed, treats drive-letter paths as `host:file` remote-archive syntax. Sidestepped with --force-local (also silently accepted by Win10's built-in bsdtar and by GNU tar). 2. Even with --force-local, MSYS2's argv-conversion layer mangles backslashes in Windows paths, so `C:\Users\...\tmp\dir` arrives at tar as `C:\Users...\dir` and it can't open the path. Passing forward-slash paths (`C:/Users/.../tmp/dir`) dodges the mangler; bsdtar and GNU tar accept them as-is. 3. sign-addon-update.mjs was tar'ing the addon directory as a subfolder (`screenshot/addon.json` inside the archive), so the client extracted to `<tmp>/screenshot/` and then failed the id+version re-check because addon.json wasn't at the root. Now the signer tars the CONTENTS of the addon dir via `tar -C <addon-dir> .`, so entries live at the archive root where the client expects them. All three surfaced from `scratchpad/decoupling-test/run-test.mjs`, which now walks the full path — sign, serve, fetch, verify, download, extract, stage, promote, backup — plus three signature-tamper negatives and the empty-pubkey short-circuit. 15/15 checks pass. |
||
|---|---|---|
| bundled-addons | ||
| dev | ||
| docs | ||
| lib | ||
| nsis | ||
| scripts | ||
| snapshots | ||
| addon-inject-preload.js | ||
| addon-tab-preload.js | ||
| addon-update-pubkeys.js | ||
| addon-updater.js | ||
| addons-host.js | ||
| address-picker-preload.js | ||
| address-picker.html | ||
| approval-preload.js | ||
| approval.html | ||
| bcnr-origin.js | ||
| bcnr-preload.js | ||
| BROWSER-PROMPT.md | ||
| chrome.html | ||
| collision-preload.js | ||
| collision.html | ||
| DESIGN-integrated-wallet.md | ||
| DESIGN-password-manager.md | ||
| downloads-preload.js | ||
| downloads.html | ||
| engine-picker-preload.js | ||
| engine-picker.html | ||
| error-preload.js | ||
| error.html | ||
| GOTCHAS.md | ||
| home-preload.js | ||
| home.html | ||
| link-status-preload.js | ||
| link-status.html | ||
| main.js | ||
| messages-preload.js | ||
| messages.html | ||
| package-lock.json | ||
| package.json | ||
| PACKAGING-PROMPT.md | ||
| PENDING.md | ||
| popover-preload.js | ||
| popover.html | ||
| preload.js | ||
| pw-fill-preload.js | ||
| pw-fill.html | ||
| README.md | ||
| RELEASE-HANDOFF.md | ||
| ROADMAP-identity-wallet.md | ||
| SESSION-PROMPT-identity-wallet.md | ||
| settings-preload.js | ||
| settings.html | ||
| sidebar-preload.js | ||
Theseus Navigator
The browser — the consumer face of the stack. Native .bch support with the
resolver built in, so a user installs one app instead of modifying their
operating system. Named for the thread through the labyrinth: the chain is the
thread.
Scope
- Electron shell (Chromium engine, no forking): tabs, address bar, history.
- In-process
.bchresolution — no system daemon, no NRPT, no OS trust-store changes; reusesbns.jsfrom the BNS repo as a library. - Record handling:
hrender,ipconnect,p/s3via in-app gateway,uredirect. - TLS via cert-verify hook (Electron
setCertificateVerifyProc) against the BNS root / on-chaintlsfingerprints — no OS store touched. - Provenance indicator: shows whether a page came from the chain / Sia / a direct server, with NFT category and record type — the decentralized padlock.
Status: not started
Build it in its own session/repo. The ready-to-paste brief is
BROWSER-PROMPT.md (a reference copy in this folder; canonical source is
D:\Dev\NameCoin\BROWSER-PROMPT.md — if they diverge, NameCoin wins). It points
here and reuses the resolver core. theseus.bch is registered and should
eventually serve the browser's own homepage over the protocol it implements.
Roadmap
BUILD-ROADMAP.md Stage 5.