From 0d8e5c4b12fcabb4901eb148b89cf9d34800fac1 Mon Sep 17 00:00:00 2001
From: Local Dev <dev@localhost>
Date: Wed, 21 Oct 2026 18:39:37 +0300
Subject: [PATCH] hermes: "on-chain registered name", not ".bch name"
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hermes handles are not tied to the .bch TLD — the user's names live on .x
today and the planned Hermes TLDs are .erm/.tel — so the hermes.x site,
the silentmode.st Hermes page and the add-on's description and panel now
say "on-chain registered name" and use alice.x / bob.x as examples.
Add-on wording ships on its own OTA; no version bump here.
---
 index.html           | 20 ++++++++++----------
 messenger/index.html | 10 +++++-----
 2 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/index.html b/index.html
index 934f068..153a398 100644
--- a/index.html
+++ b/index.html
@@ -3,19 +3,19 @@
 <head>
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
-<title>hermes.x — message anyone by their .bch name</title>
+<title>hermes.x — message anyone by their on-chain name</title>
 <meta name="description" content="Hermes: end-to-end encrypted messaging where your Bitcoin Cash name is your identity. NIP-17 sealed DMs over Nostr. No email, no phone number, no company account.">
 <link rel="icon" href="assets/favicon.svg" type="image/svg+xml">
 <link rel="mask-icon" href="assets/favicon.svg" color="#38BDF8">
 <meta property="og:type" content="website">
 <meta property="og:site_name" content="hermes.x">
-<meta property="og:title" content="hermes.x — message anyone by their .bch name">
-<meta property="og:description" content="End-to-end encrypted DMs over Nostr, addressed by your .bch name. No email, no phone, no server that can delete your account.">
+<meta property="og:title" content="hermes.x — message anyone by their on-chain name">
+<meta property="og:description" content="End-to-end encrypted DMs over Nostr, addressed by your on-chain registered name. No email, no phone, no server that can delete your account.">
 <meta property="og:url" content="https://hermes.x/">
 <meta property="og:image" content="https://hermes.x/assets/mark.svg">
 <meta name="twitter:card" content="summary">
-<meta name="twitter:title" content="hermes.x — message anyone by their .bch name">
-<meta name="twitter:description" content="Sealed-sender DMs over Nostr, addressed by .bch name.">
+<meta name="twitter:title" content="hermes.x — message anyone by their on-chain name">
+<meta name="twitter:description" content="Sealed-sender DMs over Nostr, addressed by on-chain registered name.">
 <link rel="stylesheet" href="assets/shared.css">
 </head>
 <body>
@@ -37,7 +37,7 @@
   </div>
   <h1>Message by name<span class="x">.</span></h1>
   <p class="tag">End-to-end encrypted DMs over Nostr, addressed by your
-    <code class="inline">.bch</code> name instead of a public-key string.
+    on-chain registered name instead of a public-key string.
     Your name owns your key. No email, no phone number, no company, no server
     that can delete your account.</p>
   <div class="cta">
@@ -60,7 +60,7 @@
     </div>
     <div class="card">
       <h3>Send by name <span class="src ok">live</span></h3>
-      <p>Type <code class="inline">alice.bch</code>. The client resolves the
+      <p>Type <code class="inline">alice.x</code>. The client resolves the
          name on-chain, wraps NIP-17 to the recipient's Nostr key, publishes
          to their declared relays. Sealed-sender — the relay never sees who
          sent what to whom.</p>
@@ -97,10 +97,10 @@
     Bitcoin Cash names exist to escape.</p>
   <div class="note">
     <b>The Hermes pitch.</b><br>
-    <code class="inline">alice.bch</code> publishes her Nostr pubkey as an
+    <code class="inline">alice.x</code> publishes her Nostr pubkey as an
     on-chain record. Her name certificate <i>is</i> her verified,
     seizure-resistant identity. Message anyone by their
-    <code class="inline">.bch</code> name — no phone number, no email, no ICANN,
+    on-chain registered name — no phone number, no email, no ICANN,
     no company, no server that can delete your account.
   </div>
 </section>
@@ -113,7 +113,7 @@
         <code class="inline">np</code> record. The key is derived from the
         same wallet seed as the name, so one seed backs both.</span></li>
     <li><b>Find people by name.</b>
-        <span>Type <code class="inline">bob.bch</code>. The client resolves
+        <span>Type <code class="inline">bob.x</code>. The client resolves
         it against the chain, pulls <code class="inline">np</code>
         (Nostr pubkey) and <code class="inline">nr</code> (preferred relays).
         No directory server involved.</span></li>
diff --git a/messenger/index.html b/messenger/index.html
index dc1bc45..01e43cd 100644
--- a/messenger/index.html
+++ b/messenger/index.html
@@ -4,7 +4,7 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>hermes.x/messenger — browser messenger (preview)</title>
-<meta name="description" content="The web version of Hermes: encrypted DMs over Nostr, addressed by .bch name, running in your browser. Preview of the UI; functional release pending.">
+<meta name="description" content="The web version of Hermes: encrypted DMs over Nostr, addressed by on-chain registered name, running in your browser. Preview of the UI; functional release pending.">
 <link rel="icon" href="../assets/favicon.svg" type="image/svg+xml">
 <link rel="stylesheet" href="../assets/shared.css">
 <style>
@@ -100,7 +100,7 @@
   </div>
   <h1>Messenger</h1>
   <p class="tag">Hermes in a browser tab — end-to-end encrypted DMs over Nostr,
-    addressed by <code class="inline">.bch</code> name. The desktop client has
+    addressed by on-chain registered name. The desktop client has
     the richest flavour; the web messenger meets you where you are.</p>
 </header>
 
@@ -149,7 +149,7 @@
       </div>
       <div class="thread-body">
         <div class="bubble in">hey, did you register your name yet?<span class="time">11:38</span></div>
-        <div class="bubble out">just now — bob.bch is live<span class="time">11:40</span></div>
+        <div class="bubble out">just now — bob.x is live<span class="time">11:40</span></div>
         <div class="bubble in">nice. send me the hermes.x link<span class="time">11:42</span></div>
         <div class="bubble out">https://hermes.x/messenger<span class="time">11:43</span></div>
         <div class="bubble in">great, send me the link<span class="time">11:44</span></div>
@@ -176,7 +176,7 @@
         <li>Address book (local JSON + vCard import)</li>
         <li>Sidebar panel, Ctrl+Shift+E shortcut</li>
         <li>Vault-bind: no re-typing the mnemonic</li>
-        <li>Reverse-resolve pk → .bch name</li>
+        <li>Reverse-resolve pk → on-chain name</li>
       </ul>
       <div class="cta" style="justify-content:flex-start;margin-top:1.2rem">
         <a class="btn primary" href="https://theseus.x/">Get Theseus</a>
@@ -214,7 +214,7 @@
       <span>The desktop talks to a chipnet Fulcrum directly. A browser can't
       — it needs an HTTPS gateway that answers <code class="inline">np</code>
       / <code class="inline">nr</code> for a name. The gateway is live
-      (<code class="inline">navigate.st/api/dns/alice.bch</code>) but the
+      (<code class="inline">navigate.st/api/dns/alice.x</code>) but the
       client-side cache + signature-verification path still has an edge case
       with lapsed names.</span></li>
     <li><b>Relay persistence.</b>