Sirius.X is the entry point for BCNR — Bitcoin Cash Name Registry. Register a top-level domain, register a name under one, look up records, verify anything against the chain.
Three things you can do right now. The registrar and TLD-registry UIs live at silentmode.st today; Sirius.X is the canonical home and will consolidate them here.
Pick a label, search across every TLD in the registry at once, mint the name certificate straight into your own wallet. A few cents in chain fees, no yearly renewal.
A TLD is itself a certificate on the chain. Anyone can mint one — you become the registry operator for every second-level name under it. One BCH transaction, no renewal.
Resolve any BCNR name, compare records across mirrors, and check the TLD registry snapshot against the chain. Everything is publicly verifiable.
Import your seed phrase or connect a wallet (Cashonize / Paytaca via WizardConnect) to see every name you own, review records, and update them. Your keys never leave your browser.
The browser that speaks BCNR natively. Open hello.bch in the address bar —
it just resolves. TLS verified against on-chain fingerprints, no OS trust-store install.
The full docs — TLD registry model, record types, resolver & gateway paths, mainnet pricing, verification, and the operator runbook pointer — live on their own page so they can grow without cluttering the landing.
The per-TLD registry means minting a TLD is a real, paid action — not a namespace land-grab. During the alpha, all TLD mints are operator-signed. To propose a TLD, get in touch via the channels below. The design (mainnet) adds an on-chain covenant with countersignature + tiered USD price floors: 1-char $100k, 2-char $50k, 3-char $15k, 4-char $5k, 5–8-char $1k, 9+-char $250; one-time payment (not annual). See the design doc for the full model.
Sirius.x is one of seven sibling .x names — the Silent Mode pantheon. Each project is its own on-chain certificate; each site is reachable through any BCNR resolver, plus the silentmode.st gateway for browsers without one.
The project umbrella. Redirects to silentmode.st where every pillar
has its own landing page + download hub.
The browser that speaks BCNR natively — Chromium build with the resolver baked in, no OS-level daemon or root-store install.
The forge. Forgejo instance for the ecosystem's git repos, backed by BCH wallet auth. Sirius's own source lives here.
Fire from the chain. The project's foresight / experimentation layer.
Redirects to silentmode.st/prometheus/ today.
The public gaze. Analytics, dashboards, transparency reports.
Redirects to silentmode.st/helios/ today.
Messenger. Nostr-based messaging bound to a BCNR name via the np
+ nr records. Redirects to silentmode.st/hermes/.
Sirius.X consolidates docs and registration today; three larger pieces are on the roadmap.
Sign in with your BCNR wallet, see every name you own, edit records inline, mint or renew from one place. Same self-custody as today — the portal never handles your keys.
An in-browser site editor for names you already own — the WordPress / Tilda / Wix pattern,
but the whole site persists to Sia and the name's s3 record updates on save.
Sites live where the name says they live.
The Silent Mode repo is served as a bare git tree over dumb-HTTP from the VPS. Clone it with any git client, no login. Forgejo + Sia sync for a proper decentralized backend is the next track.
git clone https://silentmode.st/sirius-x/repo/silent-mode.git
One-shot snapshot as a downloadable git bundle (works when dumb-HTTP is blocked):
curl -O https://silentmode.st/sirius-x/repo/silent-mode.bundle git clone silent-mode.bundle silent-mode
You do not have to trust that sirius.x is served by anyone specific.
The name's certificate is on the Bitcoin Cash chain; the records point to Sia; every path is
independently checkable.
node --input-type=module -e "
import { loadWallet } from './Argus/src/lib/wallet.js';
import { resolveName } from './Argus/src/lib/bns.js';
const w = await loadWallet('main');
console.log(await resolveName(w.provider, 'sirius.x'));
process.exit(0);"
The operator-signed snapshot of the TLD list is published as a Nostr replaceable event. Any relay carries it; the event's content field carries the current snapshot root.
The same content should be served from at least two independent paths. If one mirror is unavailable, the others still work. If two mirrors disagree, the on-chain record is the tiebreaker.
https://sirius.x/ (requires the local root CA)https://navigate.st/bns/sirius.xhttps://silentmode.st/bns/sirius.xs3 record on sirius.x
names the exact bucket key