Argus � the BNS public gateway (navigate.st) and its library layer. Serves BCNR names over HTTPS, verifies signed records, mints TLDs.
7bd87f2458
The old 4-layer credential blocker (sealed-off password rewriter + runtime guards) + wildcard-subdomain-origin plan is replaced by a single CSP `sandbox` directive on every /bns/ response. The browser assigns each document a unique opaque origin, so localStorage, IndexedDB, cookies, WebAuthn, service workers and the Credential Management API are all unavailable to the page — nothing to store, nothing to steal, no cross- tenant anything. No runtime guards required; the browser does it. Changes: - Add `sandbox allow-scripts allow-forms allow-popups allow-popups-to-escape-sandbox allow-top-navigation-by-user-activation allow-modals allow-downloads` to RELAY_SECURITY_HEADERS. Never `allow-same-origin` — that would hand the real origin back. - Rip out SUB_BASE / SUB_BASE_ALL / nameToSubdomainLabel / subdomainLabelToName / inbound `*.bns.navigate.st` Host-routing / apex catch-all / pathForm plumbing. No more wildcard DNS or wildcard cert needed; the sandbox gives us the same isolation on the path form. - Drop the static `rewritePasswordFields` HTML transform. With sandbox, there are no credentials to protect at the field level. - injectRelayChrome collapses to the bottom-right info chip plus one passive sign-in nudge. The nudge appears the first time the visitor focuses `<input type="password">` or pastes a BIP39 seed phrase / xprv / WIF / long hex key. It explains why sign-in won't persist (sealed view) and offers one CTA: install Theseus. Does not block typing or submit; the sandbox has already prevented the storage side. - MutationObserver wires dynamically-added password fields: wireOne matches the node itself (not just descendants), DOMContentLoaded hook catches late body content. Chip + nudge chrome stay wrapped in the existing sentinel markers so native BCDN clients can still strip them. - Chip pop text + home() landing both now point visitors at /about on navigate.st for the sealed-view explanation (shipped alongside this). - Startup log line reads "(path /bns)" only, matching the retired subdomain form. |
||
|---|---|---|
| contracts | ||
| setup | ||
| src | ||
| test | ||
| .gitignore | ||
| ariadne.config.json | ||
| BROWSER-PROMPT.md | ||
| build-web.mjs | ||
| DESIGN-collision-modes.md | ||
| DESIGN-hosting-pact.md | ||
| DESIGN-root-tld-cert.md | ||
| ENGINE.md | ||
| LICENSE | ||
| namespaces.pdf | ||
| OPERATIONS-electrum.md | ||
| package-lock.json | ||
| package.json | ||
| PROTOCOL.md | ||
| README.md | ||
| ROADMAP.md | ||
| sia-test.html | ||
BNS — Namecoin-style decentralized names on Bitcoin Cash (chipnet)
A working prototype of "Option 3": names are CashTokens name certificates on the BCH chain (no fork, no sidechain), records ride in OP_RETURN, discovery via a beacon address, and the resolver is embedded in a wallet app with a built-in browser pane — the Brave/MetaMask-browser architecture in miniature.
See PROTOCOL.md for the on-chain design and its honest limitations.
Layout
src/lib/bns.js— protocol core: payload codec, chain indexer/resolver, tx builderssrc/wallet-app.js— wallet + embedded resolver + browser UI (npm run wallet→ http://localhost:4626)src/register.js/src/update.js/src/resolve.js— CLI equivalentswallets.json— chipnet seed phrases (TESTNET ONLY — never reuse for real funds)src/lib/gen-wallets.js— one-time wallet generation (already run)
Setup
npm install- Fund the wallet with free chipnet tBCH: go to https://tbch.googol.cash/,
paste the wallet address (shown in the app sidebar or by
node src/lib/gen-wallets.js), pick chipnet, solve the captcha. ~0.001 tBCH funds hundreds of registrations. npm run walletand open http://localhost:4626
Standalone resolver daemon (make EVERY browser resolve .bch)
src/daemon/bnsd.js— DNS server (answers*.bchfrom the chain, forwards everything else upstream) + HTTP gateway that serves on-chain sites by Host header. Test unprivileged:node src/daemon/bnsd.js --dns-port 5354 --http-port 8081, thennode src/daemon/dig.js hello.bch.setup/install.ps1— run from an elevated PowerShell. Installs the daemon as a boot-time scheduled task (SYSTEM, auto-restart) and wires the OS to it:- default (
-Mode nrpt): adds an NRPT rule so only.bchqueries reach the daemon; all other DNS is untouched. -Mode full: points every adapter's DNS at 127.0.0.1 (daemon forwards non-.bch upstream, ncdns-style); original servers are saved and restored on uninstall.
- default (
setup/uninstall.ps1— reverses everything (rule/adapters/task).
HTTPS for .bch: the "BNS Local Root CA" (created on demand in ca/, keep
root-ca.key private) signs per-name certs. The daemon's :443 gateway mints
them on the fly for locally-served names; node src/lib/issue-cert.js <name>
issues one for a real server (see the coinspectrum.bch nginx vhost). The
installer trusts the root machine-wide and enables Firefox's
enterprise-roots policy; cert fingerprints are published in "tls" chain
records for pinning.
Caveats: browsers with "secure DNS" (DoH) enabled bypass the OS resolver — disable it or add an exception; ports 53/80/443 must be free.
Try it
- Register
hellowith inline HTML (a website stored entirely on-chain), then typehello.bchin the address bar — the app resolves it from the blockchain (not DNS) and renders it. - Or CLI:
node src/register.js hello '{"h":"<h1>Served from the BCH chain</h1>"}'thennode src/resolve.js hello