silentmode/site
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

hermes: "on-chain registered name", not ".bch name"

Browse source 
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.
This commit is contained in:
Local Dev 2026-10-21 18:39:37 +03:00
parent f3d9b807d9
commit 222633bebb
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
hermes/index.html
View file

@ -44,7 +44,7 @@
</div>
<h1>Hermes <span class="pill p-shipped" style="vertical-align:middle;font-size:12px;margin-left:.6rem;background:rgba(79,209,165,.12);color:#4fd1a5;padding:2px 10px;border-radius:999px">MVP · desktop</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. Same wallet
on-chain registered name instead of a public-key string. Same wallet
is your identity — no email, no phone number, no company, no server that can delete
your account.</p>
<p class="tag" style="font-size:.95rem;margin-top:.8rem">
@ -76,7 +76,7 @@
</div>
<div class="card">
<h3>Send &amp; receive by name <span class="src s-chain">live</span></h3>
<p>Type <code class="inline">alice.bch</code> — the client resolves on-chain,
<p>Type <code class="inline">alice.x</code> — the client resolves on-chain,
wraps NIP-17, publishes to the recipient's declared relays. Sealed-sender:
the relay never sees who sent what to whom.</p>
</div>
@ -112,9 +112,9 @@
Decentralized messaging bolted onto centralized identity.</p>
<div class="note"><b>The Hermes pitch.</b><br>
<code class="inline">alice.bch</code> publishes her Nostr pubkey as an on-chain
<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
Message anyone by their on-chain registered name — no phone number, no
email, no ICANN, no company, no server that can delete your account.</div>
</section>
@ -127,7 +127,7 @@
The key is derived from the same wallet seed as the name itself, 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 it against
<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>
<li><b>Send the message sealed.</b>