laantungir/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2026-01-24 19:19:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
fiatjaf_
2026-01-19 09:40:17 -03:00
committed by GitHub
parent eb252ccfc4
commit f461065c29
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
29.md
View File

@@ -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 ### 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) - *group metadata* (`kind:39000`) (optional)