Checkpoint: NIP-05 as next feature, relay config notes

CHECKPOINT-encryption.md

@@ -103,5 +103,15 @@ websocket queries; Iris shows the stored names after publish.
   published to. Keep major relays enabled so clients that don't read your own relay can
   see the profile.
 - Clients cache profiles; hard-refresh (Ctrl+Shift+R) after republishing.
-- Possible follow-ups: rename profiles (edit label + republish), NIP-05 identifiers,
+- **Next feature (agreed 2026-08-22): NIP-05 identifiers.** Live testing showed Iris
-  banner/about fields in the edit UI.
+  renders names+pictures perfectly from plain kind 0 metadata, but Yakihonne only shows
+  a proper username handle when `nip05` is present, and some newer clients
+  (phoenix.social) are picky about relay coverage. Plan: add an optional NIP-05
+  identifier field per profile (GUI + CLI), include it in published metadata, plus docs
+  or a helper for serving `.well-known/nostr.json` on the user's domain (the HTTP side
+  cannot be done by the app alone).
+- Other candidates: rename profiles (edit label + republish), banner/about fields in the
+  edit UI.
+- Relay config at time of writing (all enabled): nos.lol, relay.primal.net, l484.com
+  (user's own), damus.io, snort.social, soloco.nl; relay.nostr.band added but was
+  unreachable (handshake timeout) — retry enabling later.