First SEO push on silentmode.st, targeting Sirius as the primary
product landing page (chosen over navigate.st because a project with
pages ranks; a search box doesn't).
site/sirius/index.html:
* Title and meta description rewritten benefit-first — "Anonymous
domain names on Bitcoin Cash — Sirius" at 50 chars, meta at 170.
* H1 moved from brand-only "Sirius" to the primary keyword
"Anonymous domain names on Bitcoin Cash".
* Tag line rewritten to lead with no-KYC, no-renewals, pay-once,
register-your-own-TLD — the differentiators prospective
registrants actually search for.
* canonical + keywords meta added.
* FAQ section (10 questions) phrased exactly as people search:
"How much does a .bch domain cost?", "Can my domain be seized?",
"Can I register my own TLD?", etc. details/summary accordion,
styled inline against the existing palette.
* JSON-LD: Service schema (lowPrice $25, highPrice $500, 9 TLDs)
+ FAQPage schema mirroring the 10 FAQ answers verbatim. Both
parse cleanly.
* The in-page "vs ordinary registrar" section now links to the
full comparison page below.
site/sirius/vs.html (new): 7-way comparison across GoDaddy, Namecheap,
Cloudflare, ENS, Unstoppable Domains, Handshake, and Sirius. Targets
"X vs Y" long-tail queries. Includes BreadcrumbList + Article JSON-LD,
"where each option wins" honest-tradeoff section, and 10-year cost
projection table.
site/robots.txt (new): allow-all + explicit entries for the AI
scrapers, sitemap pointer.
site/sitemap.xml (new): primary silentmode.st surfaces with priorities
weighted to the SEO targets.
491 lines
31 KiB
HTML
491 lines
31 KiB
HTML
<!doctype html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||
<title>Anonymous domain names on Bitcoin Cash — Sirius</title>
|
||
<meta name="description" content="Register a domain name anonymously on the Bitcoin Cash chain. No KYC, no account, no renewals. Pay once with crypto. Register your own custom TLD. Served trustlessly from the chain.">
|
||
<link rel="canonical" href="https://silentmode.st/sirius">
|
||
<meta name="keywords" content="anonymous domain registration, cheap domain names, domain without KYC, decentralized domain names, blockchain domain names, Bitcoin Cash domain, BCNR, BNS, custom TLD, register your own TLD, .bch domain">
|
||
<meta property="og:type" content="website">
|
||
<meta property="og:site_name" content="Silent Mode">
|
||
<meta property="og:title" content="Anonymous domain names on Bitcoin Cash — Sirius">
|
||
<meta property="og:description" content="Register a domain name anonymously on the Bitcoin Cash chain. No KYC, no account, no renewals. Pay once with crypto. Register your own custom TLD.">
|
||
<meta property="og:url" content="https://silentmode.st/sirius">
|
||
<meta property="og:image" content="https://silentmode.st/brand/og.png">
|
||
<meta property="og:image:width" content="1200">
|
||
<meta property="og:image:height" content="630">
|
||
<meta name="twitter:card" content="summary_large_image">
|
||
<link rel="stylesheet" href="shared.css?v=20260910">
|
||
<link rel="icon" type="image/svg+xml" href="favicon.svg">
|
||
<style>
|
||
/* FAQ accordion — unstyled <details> is ugly on dark; this gives the
|
||
questions a card look that matches the rest of the page without
|
||
needing to touch shared.css. */
|
||
.faq-item{background:var(--panel,#141a24);border:1px solid var(--line,rgba(255,255,255,.09));
|
||
border-radius:12px;margin:10px 0;overflow:hidden}
|
||
.faq-item > summary{list-style:none;cursor:pointer;padding:16px 20px;font-weight:600;
|
||
color:var(--ink,#e7eaf1);font-size:16px;position:relative;padding-right:48px}
|
||
.faq-item > summary::-webkit-details-marker{display:none}
|
||
.faq-item > summary::after{content:"+";position:absolute;right:20px;top:50%;
|
||
transform:translateY(-50%);font-size:22px;color:var(--acid,#d6ff3d);line-height:1;
|
||
font-weight:300}
|
||
.faq-item[open] > summary::after{content:"−"}
|
||
.faq-item > summary:hover{color:var(--acid,#d6ff3d)}
|
||
.faq-item > p{margin:0;padding:0 20px 18px;color:var(--mut,#8b98a9);line-height:1.65;font-size:15px}
|
||
.faq-item > p a{color:var(--acid,#d6ff3d)}
|
||
.faq-item > p code{background:rgba(214,255,61,.08);padding:1px 6px;border-radius:4px;
|
||
font-size:13px;color:var(--acid,#d6ff3d)}
|
||
</style>
|
||
<!-- JSON-LD structured data — Service schema (makes Sirius eligible for
|
||
a knowledge-panel entry) + FAQPage schema (eligible for individual
|
||
Q&A rich snippets in search). Keep answers in sync with the HTML
|
||
details blocks below; divergence looks spammy to Google. -->
|
||
<script type="application/ld+json">
|
||
{
|
||
"@context": "https://schema.org",
|
||
"@type": "Service",
|
||
"name": "Sirius",
|
||
"alternateName": "Sirius.X",
|
||
"serviceType": "Decentralized domain name registry",
|
||
"description": "Anonymous domain name registration on the Bitcoin Cash chain. No KYC, no account, no renewals. Register your own custom TLD.",
|
||
"url": "https://silentmode.st/sirius",
|
||
"provider": {
|
||
"@type": "Organization",
|
||
"name": "Silent Mode",
|
||
"url": "https://silentmode.st/"
|
||
},
|
||
"areaServed": {
|
||
"@type": "GeoShape",
|
||
"name": "Worldwide"
|
||
},
|
||
"offers": {
|
||
"@type": "AggregateOffer",
|
||
"priceCurrency": "USD",
|
||
"lowPrice": "25",
|
||
"highPrice": "500",
|
||
"offerCount": "9",
|
||
"description": "One-time registration under live BCNR TLDs (.x, .bch, .p2p, .deviant, .bit, .nav, .test, .coin, .cash). No renewal fees."
|
||
}
|
||
}
|
||
</script>
|
||
<script type="application/ld+json">
|
||
{
|
||
"@context": "https://schema.org",
|
||
"@type": "FAQPage",
|
||
"mainEntity": [
|
||
{"@type":"Question","name":"How much does a domain name on Sirius cost?","acceptedAnswer":{"@type":"Answer","text":"On chipnet the cost is a few test coins. On mainnet each TLD owner sets a USD price on-chain, typically $25–$500 one-time under live TLDs (.x, .bch, .p2p, .deviant, .bit, .nav, .test, .coin, .cash). You pay once and keep the name forever — there is no annual renewal."}},
|
||
{"@type":"Question","name":"Do I need to show ID or KYC to register a .bch domain?","acceptedAnswer":{"@type":"Answer","text":"No. Sirius has no account system, no email signup, no phone verification, no address, no payment card. You pay the on-chain fee from a Bitcoin Cash wallet and the name's ownership certificate lands directly in that wallet. Nothing about who you are is attached to the name."}},
|
||
{"@type":"Question","name":"Can my domain be seized, taken down, or censored?","acceptedAnswer":{"@type":"Answer","text":"No. The ownership certificate is a CashTokens NFT that only the private key in your wallet can move. Silent Mode cannot revoke it, ICANN has no jurisdiction over it, no registrar sits between you and the name, and no court order to a company can produce one."}},
|
||
{"@type":"Question","name":"Can I register my own TLD?","acceptedAnswer":{"@type":"Answer","text":"Yes — Sirius is one of the only registries where anyone can mint a top-level domain. Any wallet can register a new TLD by paying the TLD-registry fee; you then own that TLD as an on-chain certificate, set its policy, set its name-registration price, and earn the per-name revenue every time someone registers a name under it."}},
|
||
{"@type":"Question","name":"Does my domain expire or need yearly renewal?","acceptedAnswer":{"@type":"Answer","text":"Not on today's BNS1 chipnet build — a name is yours until the certificate NFT in your wallet moves. The mainnet BNS2 build will introduce an optional lifecycle so abandoned names can be reclaimed, but owners pay only when the name is first minted; there is no yearly renewal."}},
|
||
{"@type":"Question","name":"Can I sell my .bch domain?","acceptedAnswer":{"@type":"Answer","text":"Yes. Any Sirius name can be listed on the built-in marketplace in one on-chain transaction with no escrow. You sign a partial transaction that pays you when a buyer completes it. Prices can be fixed or USD-pegged."}},
|
||
{"@type":"Question","name":"Where can I host the website for my Sirius domain?","acceptedAnswer":{"@type":"Answer","text":"Three options, pointed to by on-chain records: inline HTML (h record — the whole page lives in the Bitcoin Cash transaction), a free Sia bucket (s3 record — Silent Mode's Pithos.X gateway hosts a starter quota per name), or your own server (ip + tls records — the TLS fingerprint is pinned on-chain, no CA required)."}},
|
||
{"@type":"Question","name":"What wallets can I use to register a Sirius name?","acceptedAnswer":{"@type":"Answer","text":"The built-in browser wallet on Sirius.X (keys stay in your browser), any WizardConnect-compatible wallet including Cashonize and Paytaca, or CashConnect for direct connection. All three paths mint the certificate NFT straight to a key you control — nothing is custodial at any point."}},
|
||
{"@type":"Question","name":"How is this different from ENS, Handshake, or Unstoppable Domains?","acceptedAnswer":{"@type":"Answer","text":"Sirius runs on Bitcoin Cash — the same chain that settles the payment, no separate token to buy, no bridge, no Layer 2. Names are CashTokens NFTs you hold in your own wallet, no smart-contract custody. Resolution is one electrum query against a public beacon address — any device can be a resolver. And anyone can mint their own TLD."}},
|
||
{"@type":"Question","name":"Can I resolve .bch names in a normal browser like Chrome or Firefox?","acceptedAnswer":{"@type":"Answer","text":"Yes, two ways. Zero-install: open any name through navigate.st, the public gateway that reads the chain for you. Local, trustless: install the Theseus Navigator (Chromium-based, speaks .bch natively) or the Ariadne Resolver system-wide service, and any browser on your machine opens Sirius names directly."}}
|
||
]
|
||
}
|
||
</script>
|
||
</head>
|
||
<body>
|
||
|
||
<nav class="topnav">
|
||
<a class="brand" href="./"><svg class="logo" viewBox="0 0 32 20" aria-hidden="true"><rect class="l1" x="1.5" y="3.5" width="17" height="13" rx="6.5" ry="6.5" fill="none" stroke-width="2.6"/><rect class="l2" x="13.5" y="3.5" width="17" height="13" rx="6.5" ry="6.5" fill="none" stroke-width="2.6"/></svg>Silent <span class="g">Mode</span></a>
|
||
<a href="theseus">Theseus</a>
|
||
<a href="prometheus">Prometheus</a>
|
||
<a href="sirius" class="here">Sirius</a>
|
||
<a href="hephaestus">Hephaestus</a>
|
||
<a href="helios">Helios</a>
|
||
<a href="hermes">Hermes</a>
|
||
<a href="tools">Tools</a>
|
||
</nav>
|
||
|
||
<header class="hero">
|
||
<div class="mark" style="font-size:52px">⭐</div>
|
||
<h1>Anonymous domain names on <span class="g">Bitcoin Cash</span></h1>
|
||
<p class="tag"><b>Sirius</b> is Silent Mode's decentralized domain registry.
|
||
Register a name without an account, without KYC, without renewal fees — one
|
||
on-chain transaction, pay once with crypto, keep forever in a wallet you
|
||
control. No registrar, no ICANN, no DNS root. Resolvers read the chain
|
||
directly. You can even <b>register your own TLD</b> and sell names under it.</p>
|
||
<div class="cta">
|
||
<a class="btn acid" href="/sirius-x/#search-input">Open Sirius.X — register a name</a>
|
||
<a class="btn ghost" href="#how">How BNS1 works</a>
|
||
<a class="btn ghost" href="#tlds">Live TLDs</a>
|
||
</div>
|
||
<p style="margin:1.4rem 0 0;color:var(--dim);font-size:13px">
|
||
<b style="color:var(--mut)">Sirius.X</b> is the sovereign registrar site, served from its own name.
|
||
Mirror: <a href="/sirius-x/">silentmode.st/sirius-x/</a> ·
|
||
gateway: <a href="https://navigate.st/bns/sirius.x/">navigate.st/bns/sirius.x/</a> ·
|
||
native with a resolver: <a href="https://sirius.x/"><code class="inline">https://sirius.x/</code></a>
|
||
</p>
|
||
</header>
|
||
|
||
<div class="wrap">
|
||
|
||
<!-- ============ THE PROTOCOL IN THREE PARTS ============ -->
|
||
<section class="plain">
|
||
<h2>BNS1 — the protocol in three parts</h2>
|
||
<p class="lede">A minimal Namecoin-style name protocol on Bitcoin Cash. No fork, no
|
||
sidechain, no new blockchain — three ordinary mechanisms of BCH doing three
|
||
different jobs.</p>
|
||
|
||
<div class="grid">
|
||
<div class="card">
|
||
<span class="pill p-live">ownership</span>
|
||
<h3>CashTokens certificate</h3>
|
||
<p>An immutable NFT whose commitment is the UTF-8 name. Whoever holds the
|
||
certificate owns the name. Consensus guarantees nobody can mint another
|
||
output in the same category without spending it.</p>
|
||
</div>
|
||
<div class="card">
|
||
<span class="pill p-live">data</span>
|
||
<h3>OP_RETURN payload</h3>
|
||
<p>A tiny JSON payload prefixed <code class="inline">BNS1</code> — the name's
|
||
records (URL, inline HTML page, IPv4, cashaddr, Sia bucket, TLS
|
||
fingerprint). Total budget: <b>≤ 200 bytes</b>.</p>
|
||
</div>
|
||
<div class="card">
|
||
<span class="pill p-live">discovery</span>
|
||
<h3>Beacon dust output</h3>
|
||
<p>Every protocol transaction pays <code class="inline">600 sat</code> to a
|
||
well-known beacon address. Calling <code class="inline">get_history</code>
|
||
on that address enumerates every registration and update ever made — no
|
||
indexer to trust, no server between you and the answer.</p>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- ============ RECORDS ============ -->
|
||
<section id="records">
|
||
<h2>What you can attach to a name</h2>
|
||
<p class="lede">Seven record types cover the space between "point at any URL" and
|
||
"the whole website lives in this transaction". Records travel in the same
|
||
<code class="inline">OP_RETURN</code> as the name itself; the total payload stays
|
||
inside 200 bytes.</p>
|
||
|
||
<table>
|
||
<tr><th>Record</th><th>What it holds</th><th>Used for</th></tr>
|
||
<tr><td><code>u</code></td><td>An HTTPS URL</td>
|
||
<td>Redirect the name at any existing site</td></tr>
|
||
<tr><td><code>h</code></td><td>Inline HTML</td>
|
||
<td>A tiny website served entirely from the transaction — no host, anywhere</td></tr>
|
||
<tr><td><code>a</code></td><td>A cashaddr</td>
|
||
<td>Payments — the "send to <code class="inline">alice.bch</code>" use case</td></tr>
|
||
<tr><td><code>ip</code></td><td>IPv4 address</td>
|
||
<td>Point DNS directly at a server you run for the name</td></tr>
|
||
<tr><td><code>p</code></td><td>An upstream URL</td>
|
||
<td>Reverse-proxy an existing site — address bar stays on the BNS name</td></tr>
|
||
<tr><td><code>s3</code></td><td><code>bucket/key</code> or <code>bucket/prefix/</code></td>
|
||
<td>A full multi-file site on the Sia storage network</td></tr>
|
||
<tr><td><code>tls</code></td><td>SHA-256 of the DER certificate</td>
|
||
<td>Pin your server's TLS cert so nobody can MITM the connection</td></tr>
|
||
</table>
|
||
</section>
|
||
|
||
<!-- ============ HOW REGISTRATION WORKS ============ -->
|
||
<section id="how">
|
||
<h2>How registration works</h2>
|
||
<ol class="steps">
|
||
<li><b>Pick a name.</b>
|
||
<span>Labels: <code class="inline">[a-z0-9-]{1,32}</code>. Any TLD you like —
|
||
the chain decides what exists, not a committee. Search availability on the
|
||
<a href="/sirius-x/#search-input">Sirius.X registration page</a>.</span></li>
|
||
<li><b>Mint the certificate (a REG transaction).</b>
|
||
<span>One BCH transaction simultaneously mints an immutable CashTokens
|
||
certificate whose commitment is your name, publishes the records as a
|
||
<code class="inline">BNS1</code>-prefixed OP_RETURN, and pays 600 sat to the
|
||
beacon so every resolver can find it. First valid <code class="inline">REG</code>
|
||
wins.</span></li>
|
||
<li><b>Update records at any time (a UPD transaction).</b>
|
||
<span>A signed transaction that spends and returns your certificate to
|
||
yourself, carrying the new records. Only the certificate holder can do this,
|
||
because a vout in a name's category is only possible if a vin held it.</span></li>
|
||
<li><b>Transfer by sending the certificate.</b>
|
||
<span>Sending the certificate to another wallet transfers the name. No beacon
|
||
transaction needed — the certificate <i>is</i> the ownership token.</span></li>
|
||
</ol>
|
||
|
||
<div class="cta" style="justify-content:flex-start;margin-top:1.6rem">
|
||
<a class="btn acid" href="/sirius-x/#search-input">Start with a name search on Sirius.X</a>
|
||
</div>
|
||
</section>
|
||
|
||
<!-- ============ WALLETS ============ -->
|
||
<section id="wallets">
|
||
<h2>Wallets that can register a name</h2>
|
||
<p class="lede">Registration is a normal Bitcoin Cash transaction shape with a small
|
||
protocol twist: the certificate's identity is derived from the outpoint spent at
|
||
input 0, so the buyer must choose the coin, not the wallet. Any wallet that can
|
||
build a transaction to that spec works.</p>
|
||
|
||
<div class="grid">
|
||
<div class="card">
|
||
<span class="pill p-live">works today</span>
|
||
<h3>Built-in browser wallet</h3>
|
||
<p>Generated in your browser, seed encrypted with PBKDF2 → AES-GCM in
|
||
<code class="inline">localStorage</code>, never transmitted. The registration
|
||
page can search, quote, sign and broadcast in one flow. Self-custody
|
||
throughout — the registrar never touches the certificate.</p>
|
||
</div>
|
||
<div class="card">
|
||
<span class="pill p-live">works today</span>
|
||
<h3>WizardConnect <span class="src s-tor">LGPL</span></h3>
|
||
<p>Pairs the registration page with an external wallet over NIP-17 gift-wrap
|
||
messages — pass-through signing, so the dApp builds the exact transaction
|
||
and the wallet's key just signs. Currently: <b>Cashonize v0.9+</b> on
|
||
chipnet.</p>
|
||
</div>
|
||
<div class="card">
|
||
<span class="pill p-designed">deferred</span>
|
||
<h3>CashConnect</h3>
|
||
<p>Wallet-orchestrated, not pass-through — the wallet auto-selects UTXOs. That
|
||
collides with the genesis-input rule that fixes the certificate's identity
|
||
to a specific coin. May return once its <code class="inline">bch_executeAction</code>
|
||
model ships.</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="note"><b>Self-custody by construction.</b> The certificate lands at the
|
||
buyer's own address in the same transaction as the fee payment, so the registrar
|
||
never <i>holds</i> the name. The acceptance test explicitly checks that no
|
||
certificate exists at the fee address after each registration.</div>
|
||
</section>
|
||
|
||
<!-- ============ TLDS ============ -->
|
||
<section id="tlds">
|
||
<h2>TLDs live on chipnet today</h2>
|
||
<p class="lede">BNS on BCH is deliberately TLD-agnostic — the rightmost label is
|
||
the registry. There is no pre-existing root; the first registration under a new
|
||
suffix is what makes that TLD exist. Below is the working set as of today.</p>
|
||
|
||
<table>
|
||
<tr><th>TLD</th><th>Note</th></tr>
|
||
<tr><td><code>.bch</code></td><td>The original TLD; bare on-chain names default to it</td></tr>
|
||
<tr><td><code>.p2p</code></td><td>Peer-to-peer software and services</td></tr>
|
||
<tr><td><code>.deviant</code></td><td>The Deviant division's namespace (Silent Mode's parent house)</td></tr>
|
||
<tr><td><code>.bit</code></td><td>Namecoin's legacy TLD, brought under BNS</td></tr>
|
||
</table>
|
||
|
||
<div class="note"><b>New TLDs.</b> Because there is no root registry to negotiate
|
||
with, a new TLD is simply the first registration under a new suffix. Silent Mode's
|
||
resolver clients will mint TLS certificates only for TLDs on a configured list
|
||
(the local CA is name-constrained) — adding a TLD to that trust list is a
|
||
resolver config change, not a chain change.</div>
|
||
</section>
|
||
|
||
<!-- ============ LIVE NAMES ============ -->
|
||
<section id="live">
|
||
<h2>Live names on chipnet</h2>
|
||
<p class="lede">These are actually registered on chipnet, right now, resolving
|
||
through the relay and every Silent Mode client. Each demonstrates one record type
|
||
from the list above.</p>
|
||
|
||
<table>
|
||
<tr><th>Name</th><th>Backing record</th></tr>
|
||
<tr><td><a href="https://navigate.st/bns/hello.bch"><code>hello.bch</code></a></td>
|
||
<td><span class="src s-chain">h</span> — a page inside the transaction itself</td></tr>
|
||
<tr><td><a href="https://navigate.st/bns/silentmode.bch"><code>silentmode.bch</code></a></td>
|
||
<td><span class="src s-chain">h</span> — this project's own on-chain demo</td></tr>
|
||
<tr><td><a href="https://navigate.st/bns/coinspectrum.bch"><code>coinspectrum.bch</code></a></td>
|
||
<td><span class="src s-srv">ip · p · tls</span> — a full site on an ordinary server, pinned by TLS fingerprint</td></tr>
|
||
<tr><td><a href="https://navigate.st/bns/coinspectrum.deviant.bch"><code>coinspectrum.deviant.bch</code></a></td>
|
||
<td><span class="src s-sia">s3</span> — a full multi-file site on the Sia storage network</td></tr>
|
||
<tr><td><a href="https://navigate.st/bns/siatest.bch"><code>siatest.bch</code></a></td>
|
||
<td><span class="src s-sia">s3</span> — earlier Sia test</td></tr>
|
||
<tr><td><a href="https://navigate.st/bns/argo.bch"><code>argo.bch</code></a></td>
|
||
<td><span class="src s-chain">h</span> — the future hosting-pact brand</td></tr>
|
||
<tr><td><a href="https://navigate.st/bns/theseus.bch"><code>theseus.bch</code></a></td>
|
||
<td><span class="src s-chain">h</span> — the browser's brand page</td></tr>
|
||
<tr><td><a href="https://navigate.st/bns/demo.p2p"><code>demo.p2p</code></a></td>
|
||
<td>Multi-TLD proof — same chain, different rightmost label</td></tr>
|
||
</table>
|
||
</section>
|
||
|
||
<!-- ============ VS ICANN ============ -->
|
||
<section id="vs">
|
||
<h2>Sirius vs an ordinary registrar</h2>
|
||
<p class="lede">Short version — the full breakdown across GoDaddy, Namecheap,
|
||
Cloudflare, ENS, Unstoppable Domains, and Handshake lives on the
|
||
<a href="vs"><b>comparison page</b></a>.</p>
|
||
<table>
|
||
<tr><th>What you get</th><th>Ordinary registrar</th><th>Sirius</th></tr>
|
||
<tr><td>How ownership is proven</td>
|
||
<td>A row in the registry's database</td>
|
||
<td>A CashTokens NFT in your wallet</td></tr>
|
||
<tr><td>Who can revoke it</td>
|
||
<td>The registrar, the registry, ICANN, a court order to any of them</td>
|
||
<td>Nobody — the certificate is an immutable NFT</td></tr>
|
||
<tr><td>Renewal</td>
|
||
<td>Yearly — miss it and the name is auctioned</td>
|
||
<td>Never on chipnet BNS1; mainnet BNS2 will have a lifecycle (below)</td></tr>
|
||
<tr><td>Cost per registration</td>
|
||
<td>$8 – $30 / year, forever</td>
|
||
<td>Chipnet: worthless test coins. Mainnet BNS2 target: ~$10–20 to register & renew</td></tr>
|
||
<tr><td>Identity required</td>
|
||
<td>Email, sometimes phone, sometimes address, always payment method</td>
|
||
<td>A wallet — no email, no phone, no card, no KYC</td></tr>
|
||
<tr><td>DNS resolution</td>
|
||
<td>ICANN → TLD registry → registrar's nameservers → you</td>
|
||
<td>Any electrum server reads the chain; your resolver does the rest</td></tr>
|
||
<tr><td>Web presence</td>
|
||
<td>Depends on a hosting provider that can suspend you</td>
|
||
<td>Point <code>h</code> at inline HTML, <code>s3</code> at Sia, or <code>ip</code>/<code>p</code> at any server you run</td></tr>
|
||
</table>
|
||
</section>
|
||
|
||
<!-- ============ FAQ ============ -->
|
||
<!-- Keyword-phrased FAQ. Written to match how prospective registrants
|
||
actually search, and marked up with the FAQPage JSON-LD further
|
||
down so Google can surface individual questions as rich snippets. -->
|
||
<section id="faq">
|
||
<h2>Frequently asked questions</h2>
|
||
|
||
<details class="faq-item">
|
||
<summary>How much does a domain name on Sirius cost?</summary>
|
||
<p>On chipnet (the live test network today) the cost is a few test coins — effectively free, used for development. On mainnet, each TLD owner sets their own price in USD on-chain, typically <b>$25 – $500 one-time</b> for a brand-new name under one of the live TLDs (<code>.x</code>, <code>.bch</code>, <code>.p2p</code>, <code>.deviant</code>, <code>.bit</code>, <code>.nav</code>, <code>.test</code>, <code>.coin</code>, <code>.cash</code>). <b>You pay once and keep the name forever</b> — there is no annual renewal.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>Do I need to show ID or KYC to register a .bch domain?</summary>
|
||
<p>No. Sirius has no account system, no email signup, no phone verification, no address or payment card. You pay the on-chain fee from a Bitcoin Cash wallet (built-in web wallet, Cashonize, Paytaca, or any WizardConnect-compatible wallet), and the name's ownership certificate lands directly in that wallet. Nothing about who you are is attached to the name.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>Can my domain be seized, taken down, or censored?</summary>
|
||
<p>No. The ownership certificate is a <b>CashTokens NFT</b> that only the private key in your wallet can move. Silent Mode cannot revoke it, ICANN has no jurisdiction over it, no registrar sits between you and the name, and no court order to a company can produce one. The only way the name changes hands is you signing a transaction yourself — or the mainnet BNS2 lifecycle naturally expiring if you let it.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>Can I register my own TLD?</summary>
|
||
<p>Yes — Sirius is one of the only registries where <b>anyone can mint a top-level domain</b>. Any wallet can register a new TLD by paying the TLD-registry fee; you then own that TLD as an on-chain certificate, set its policy (public, co-sign-approval, or private), set its own name-registration price, and earn the per-name revenue every time someone registers a name under it. See the <a href="/sirius-x/docs/#tld-registry">TLD registry docs</a>.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>Does my domain expire or need yearly renewal?</summary>
|
||
<p>Not on today's BNS1 chipnet build — a name is yours until the certificate NFT in your wallet moves. The mainnet BNS2 build will introduce an optional lifecycle so abandoned names can be reclaimed, but owners pay only when the name is first minted; there is <b>no yearly renewal to GoDaddy or anyone else</b>.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>Can I sell my .bch domain?</summary>
|
||
<p>Yes. Any Sirius name can be listed on the built-in marketplace in <b>one on-chain transaction with no escrow</b>: you sign a partial transaction that pays you when a buyer completes it. Prices can be fixed or USD-pegged. See the <a href="/sirius-x/market/">Sirius.X marketplace</a>.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>Where can I host the website for my Sirius domain?</summary>
|
||
<p>Three options, all pointed to by on-chain records on the name itself: inline HTML (<code>h</code> record — the whole page lives in the Bitcoin Cash transaction), a <b>free</b> Sia bucket (<code>s3</code> record — Silent Mode's Pithos.X gateway hosts a starter quota per name), or your own server (<code>ip</code> + <code>tls</code> records — the TLS certificate's SHA-256 is pinned on-chain, no CA required). The resolver picks whichever is set.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>What wallets can I use to register a Sirius name?</summary>
|
||
<p>The built-in browser wallet on <a href="/sirius-x/">Sirius.X</a> (PBKDF2 + AES-GCM, keys stay in your browser), any <b>WizardConnect-compatible wallet</b> including Cashonize and Paytaca, or <b>CashConnect</b> for direct connection. All three paths mint the certificate NFT straight to a key you control — nothing is custodial at any point.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>How is this different from ENS, Handshake, or Unstoppable Domains?</summary>
|
||
<p>Sirius runs on Bitcoin Cash — the same chain that already settles the payment, no separate token to buy, no bridge, no Layer 2. Names are <b>CashTokens NFTs</b> you hold in your own wallet (no smart-contract custody). Resolution is one electrum query against a public beacon address — any device can be a resolver, no gateway required. And anyone can mint their own TLD, not just a fixed set defined at launch.</p>
|
||
</details>
|
||
|
||
<details class="faq-item">
|
||
<summary>Can I resolve .bch names in a normal browser like Chrome or Firefox?</summary>
|
||
<p>Yes, two ways. Zero-install: open any name through <a href="https://navigate.st/">navigate.st</a>, the public gateway that reads the chain for you. Local, trustless: install the <a href="/theseus/">Theseus Navigator</a> (Chromium-based, speaks <code>.bch</code> natively) or the <a href="/ariadne-x/">Ariadne Resolver</a> system-wide service, and any browser on your machine opens Sirius names directly.</p>
|
||
</details>
|
||
</section>
|
||
|
||
<!-- ============ COMING NEXT — BNS2 ============ -->
|
||
<section id="bns2">
|
||
<h2>Coming next — BNS2 & the covenant registry</h2>
|
||
<p class="lede">BNS1 is the chipnet prototype. The mainnet version, BNS2, adds two
|
||
consensus-enforced pieces the prototype leaves as indexer policy. Both are
|
||
designed on paper — the specs live in
|
||
<code class="inline">Decentralized.DNS/</code> — and both wait on the mainnet cutover.</p>
|
||
|
||
<div class="grid">
|
||
<div class="card">
|
||
<span class="pill p-designed">designed</span>
|
||
<h3>Covenant-run registry</h3>
|
||
<p>Certificates live in a CashScript covenant that enforces one certificate per
|
||
name at consensus, not by indexer agreement. Same covenant enforces a
|
||
lifecycle: ACTIVE → (6–12 months) IDLE → OPEN. The owner's option to reclaim
|
||
during IDLE is 50–100× cheaper than a stranger's takeover, so the grace
|
||
period is real: a takeover only ever happens when the owner is genuinely gone.</p>
|
||
</div>
|
||
<div class="card">
|
||
<span class="pill p-designed">designed</span>
|
||
<h3>Commit–reveal (<code>CMT</code> op)</h3>
|
||
<p>A front-running defence. Publish a hash of your name first (with a 16-byte
|
||
salt), reveal the name later; the reveal that points at the oldest valid
|
||
commit wins. An attacker who sees the reveal cannot produce an older commit,
|
||
because blocks are already written.</p>
|
||
</div>
|
||
<div class="card">
|
||
<span class="pill p-designed">designed</span>
|
||
<h3>Trustless purchase</h3>
|
||
<p>Scan-to-sign registration for airgapped SPV wallets: the site builds an
|
||
unsigned transaction, the wallet signs it on a separate device via QR, the
|
||
buyer broadcasts. No relay, no connector, no third party at any point.</p>
|
||
</div>
|
||
</div>
|
||
|
||
<div class="note warn"><b>Why lifecycle matters — the Namecoin lesson.</b> A study
|
||
of Namecoin found ~120,000 <code class="inline">.bit</code> names registered and
|
||
<b>28</b> in actual use. Names live forever mean the interesting ones get
|
||
squatted forever. BNS2's covenant expiry is the design that avoids that trap
|
||
without ever letting an active owner lose a name they still use.</div>
|
||
</section>
|
||
|
||
<!-- ============ HONEST LIMITS ============ -->
|
||
<section id="limits">
|
||
<h2>Honest limitations of the current chipnet build</h2>
|
||
<div class="grid">
|
||
<div class="card">
|
||
<h3>Uniqueness is indexer policy</h3>
|
||
<p>BNS1 depends on resolvers agreeing that "first valid <code class="inline">REG</code>
|
||
wins". Consensus does not enforce it yet — that is what the covenant registry
|
||
above adds for mainnet.</p>
|
||
</div>
|
||
<div class="card">
|
||
<h3>No front-running defence yet</h3>
|
||
<p>An observer of the mempool can copy your <code class="inline">REG</code> and
|
||
race it. Does not matter on chipnet; matters the instant names have value.
|
||
The commit-reveal spec above is written; not implemented on chipnet.</p>
|
||
</div>
|
||
<div class="card">
|
||
<h3>Names live forever (for now)</h3>
|
||
<p>BNS1 has no expiry. The covenant registry adds the ACTIVE → IDLE → OPEN
|
||
lifecycle; BNS1 keeps it flat because the mistake cost on chipnet is zero.</p>
|
||
</div>
|
||
<div class="card">
|
||
<h3>Records ≤ 200 bytes</h3>
|
||
<p>The whole payload including <code class="inline">BNS1</code> prefix and JSON
|
||
fits in one OP_RETURN. Enough for URLs, cashaddrs, IPs and Sia keys —
|
||
inline HTML (<code class="inline">h</code>) is a tiny page, not a full site.
|
||
Bigger sites use <code class="inline">s3</code>.</p>
|
||
</div>
|
||
<div class="card">
|
||
<h3>Beacon is a keyed address</h3>
|
||
<p>Prototype convenience — production would use a keyless constant script so no
|
||
one can be pressured over the beacon key.</p>
|
||
</div>
|
||
<div class="card">
|
||
<h3>Everything is chipnet</h3>
|
||
<p>Mainnet migration is a separate transaction and comes after BNS2 lands. All
|
||
names, coins and mistakes on chipnet are worthless — that is the point of
|
||
doing it there first.</p>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
|
||
</div>
|
||
|
||
<footer>
|
||
<div>Silent Mode — a Deviant project.</div>
|
||
<div class="fine">Named for Sirius, the brightest star — a fixed reference everyone
|
||
sees the same way. Protocol: <code class="inline">Decentralized.DNS/PROTOCOL.md</code>
|
||
(BNS1) plus <code class="inline">DESIGN-covenant-registry.md</code> and
|
||
<code class="inline">PROTOCOL-ADDENDUM-commit-reveal.md</code> (BNS2 additions).</div>
|
||
</footer>
|
||
|
||
</body>
|
||
</html>
|