From 4cbb672d1cf6e0af2b4c09c9b33e97f7964ce36e Mon Sep 17 00:00:00 2001 From: earonesty Date: Sat, 13 May 2023 07:39:01 -0700 Subject: Fix docs from kind0 to kind33 https://github.com/nostr-protocol/nips/issues/376 --- 28.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '28.md') diff --git a/28.md b/28.md index 169ae4f..9f9302f 100644 --- a/28.md +++ b/28.md @@ -37,7 +37,7 @@ In the channel creation `content` field, Client SHOULD include basic channel met Update a channel's public metadata. -Clients and relays SHOULD handle kind 41 events similar to kind 0 `metadata` events. +Clients and relays SHOULD handle kind 41 events similar to kind 33 replaceable events, where the information is used to update the metadata, without modifying the event id for the channel. Clients SHOULD ignore kind 41s from pubkeys other than the kind 40 pubkey. -- cgit v1.2.3 From 26194822005836a8ce690009fc636e0fe71802e6 Mon Sep 17 00:00:00 2001 From: earonesty Date: Sat, 13 May 2023 07:42:40 -0700 Subject: More explicit --- 28.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '28.md') diff --git a/28.md b/28.md index 9f9302f..62ab398 100644 --- a/28.md +++ b/28.md @@ -37,7 +37,7 @@ In the channel creation `content` field, Client SHOULD include basic channel met Update a channel's public metadata. -Clients and relays SHOULD handle kind 41 events similar to kind 33 replaceable events, where the information is used to update the metadata, without modifying the event id for the channel. +Clients and relays SHOULD handle kind 41 events similar to kind 33 replaceable events, where the information is used to update the metadata, without modifying the event id for the channel. Only the most recent kind 41 is needed to be stored. Clients SHOULD ignore kind 41s from pubkeys other than the kind 40 pubkey. -- cgit v1.2.3