From 222633bebb32bfb869e29a8557aad502d804acbb Mon Sep 17 00:00:00 2001 From: Local Dev 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. --- hermes/index.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/hermes/index.html b/hermes/index.html index 877257a..e28dd04 100644 --- a/hermes/index.html +++ b/hermes/index.html @@ -44,7 +44,7 @@

Hermes MVP · desktop

End-to-end encrypted DMs over Nostr, addressed by your - .bch 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.

@@ -76,7 +76,7 @@

Send & receive by name live

-

Type alice.bch — the client resolves on-chain, +

Type alice.x — 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.

@@ -112,9 +112,9 @@ Decentralized messaging bolted onto centralized identity.

The Hermes pitch.
- alice.bch publishes her Nostr pubkey as an on-chain + alice.x publishes her Nostr pubkey as an on-chain record. Her name certificate is her verified, seizure-resistant identity. - Message anyone by their .bch 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.
@@ -127,7 +127,7 @@ The key is derived from the same wallet seed as the name itself, so one seed backs both.
  • Find people by name. - Type bob.bch. The client resolves it against + Type bob.x. The client resolves it against the chain, pulls np (Nostr pubkey) and nr (preferred relays). No directory server involved.
  • Send the message sealed.