From 6834e8bf8aaf34f2df9b40ef306c1a43f0d631c2 Mon Sep 17 00:00:00 2001 From: Anderson Juhasc Date: Wed, 15 Jul 2026 21:10:33 -0300 Subject: [PATCH] NIP-29: invite code suffix for group identifiers (#2380) --- 29.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/29.md b/29.md index 4c03cb42..5c8dcbea 100644 --- a/29.md +++ b/29.md @@ -22,6 +22,14 @@ Relays are supposed to generate the events that describe group metadata and grou 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. +An invite code may be appended to the group identifier: + +``` +naddr1...?invite= +``` + +Clients should use this code in the `code` tag of the `kind:9021` join request. Since the bech32 charset doesn't include `?`, everything before the `?` is still a valid identifier on its own, so clients that don't understand the suffix can just ignore it. + ## 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_.