From bb5e05c6023fa0645a1c32710e3c895a256881f9 Mon Sep 17 00:00:00 2001 From: sepehr-safari Date: Mon, 14 Sep 2026 17:26:31 +0300 Subject: [PATCH] Plaza answers to plaza@zignostr.com The domain had one key on it. `_` and `sepehr` both point at mine, so a client asked to verify Plaza's account found nothing here to check it against and drew the account unverified. Plaza signs with its own key, so it needs its own name rather than a second alias for mine. The route already honours `?name=` and returns only the mapping that was asked for, so this is one more entry in the map and nothing else changes shape. The endpoint is half of it. The account's kind-0 has to carry "nip05": "plaza@zignostr.com" before any client draws the check. --- app/.well-known/nostr.json/route.js | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/app/.well-known/nostr.json/route.js b/app/.well-known/nostr.json/route.js index 7aedeac..e6f22fd 100644 --- a/app/.well-known/nostr.json/route.js +++ b/app/.well-known/nostr.json/route.js @@ -7,11 +7,15 @@ const PUBKEY = '3e294d2fd339bb16a5403a86e3664947dd408c4d87a0066524f8a573ae53ca8e' +const PLAZA_PUBKEY = + '218cd85be35f1558286e68aae8fc2b33a10d19f0c2c8e05d2cf0b42653332124' + // name -> hex pubkey (lowercase). `_` is the root identifier: sepehr@zignostr.com // with no local part resolves to it per NIP-05. const NAMES = { _: PUBKEY, sepehr: PUBKEY, + plaza: PLAZA_PUBKEY, } // The response depends on the query string, so never prerender or cache it.