From 175ad95111b2c669c3dc74f4fa577f42ba6c5ff4 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Wed, 20 May 2026 10:56:50 -0300 Subject: [PATCH] nip29: remove poorly-thought group identifier recommendation. --- 29.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/29.md b/29.md index 9d20ef2e..a82f6fdf 100644 --- a/29.md +++ b/29.md @@ -20,11 +20,7 @@ Relays are supposed to generate the events that describe group metadata and grou ## Group identifier -A group may be identified by a string in the format `'`. For example, a group with _id_ `abcdef` hosted at the relay `wss://groups.nostr.com` would be identified by the string `groups.nostr.com'abcdef`. - -Group identifiers must be strings restricted to the characters `a-z0-9-_`, and SHOULD be random in order to avoid name collisions. - -When encountering just the `` without the `'`, clients MAY infer `_` as the group id, which is a special top-level group dedicated to relay-local discussions. +A group may be identified by a `naddr1...` code to its `kind:39000` metadata event, with the public key set to the relay `self` public key, the `d` identifier set to the group id, the kind set to `39000` and a relay hint to the relay that is hosting the group. ## The `h` tag