nip29: clarify what the relay key means (#2190)

1 files changed, 1 insertions, 1 deletions

diff --git a/29.md b/29.md
index d612bc7..85f47ca 100644
--- a/29.md
+++ b/29.md
@@ -134,7 +134,7 @@ It's expected that the group state (of who is an allowed member or not, who is a
 
 ### Group metadata events
 
-These events contain the group id in a `d` tag instead of the `h` tag. They MUST be created by the relay master key only and a single instance of each (or none) should exist at all times for each group. They are merely informative but should reflect the latest group state (as it was changed by moderation events over time).
+These events contain the group id in a `d` tag instead of the `h` tag. They MUST be created by the relay master key only (as stated by the [NIP-11](11.md) `"self"` pubkey) and a single instance of each (or none) should exist at all times for each group. They are merely informative but should reflect the latest group state (as it was changed by moderation events over time).
 
 - *group metadata* (`kind:39000`) (optional)