remove naddr stuff, use a different identifier format.

1 files changed, 4 insertions, 2 deletions

diff --git a/29.md b/29.md
index a267ea7..3d648dc 100644
--- a/29.md
+++ b/29.md
@@ -18,6 +18,10 @@ Normally a group will originally belong to one specific relay, but the community
 
 Relays are supposed to generate the events that describe group metadata and group admins. These are parameterized replaceable events signed by the relay keypair directly, with the group _id_ as the `d` tag.
 
+## Group identifier
+
+A group may be identified by a string in the format `<host>'<group-id>`. 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`.
+
 ## The `h` tag
 
 Events sent by users to groups (chat messages, text notes, moderation events etc) must have an `h` tag with the value set to the group _id_.
@@ -151,8 +155,6 @@ If the group is forked and hosted in multiple relays, there will be multiple ver
 
 `name`, `picture` and `about` are basic metadata for the group for display purposes. `public` signals the group can be _read_ by anyone, while `private` signals that only AUTHed users can read. `open` signals that anyone can request to join and the request will be automatically granted, while `closed` signals that members must be pre-approved or that requests to join will be manually handled.
 
-The [NIP-19](19.md) `naddr` pointer for this event including with a mandatory relay can be used as the canonical group identifier.
-
 - *group admins* (`kind:39001`) (optional)
 
 Similar to the group metadata, this event is supposed to be generated by relays that host the group.