From e9bc1d30252f9a974a0cc81f4f426c01d19f9b8c Mon Sep 17 00:00:00 2001 From: Anderson Juhasc Date: Mon, 15 Jun 2026 16:04:03 -0300 Subject: [PATCH] NIP-29: add banner tag to group metadata (kind:39000) --- 29.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/29.md b/29.md index d3acd6a068..bc1579d6de 100644 --- a/29.md +++ b/29.md @@ -152,6 +152,7 @@ If the group is forked and hosted in multiple relays, there will be multiple ver ["d", ""], ["name", "Pizza Lovers"], ["picture", "https://pizza.com/pizza.png"], + ["banner", "https://pizza.com/banner.png"], ["about", "a group for people who love pizza"], ["private"], ["closed"], @@ -161,7 +162,7 @@ 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. +- `name`, `picture`, `banner` and `about` are basic metadata for the group for display purposes. - `private` indicates that only members can _read_ group messages. Omitting this tag indicates that anyone can read group messages. - `restricted` indicates that only members can _write_ messages to the group. Omitting this tag indicates that anyone can send messages to the group. - `hidden` indicates that relays should hide group metadata from non-members. Omitting this tag indicates that anyone can request group metadata events.