From 854871a5c124392e362344f81aaf6fe1edee5f57 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 19 Jan 2026 11:42:08 +0000 Subject: [PATCH] fix: pass protocol and identifier directly to chat window Fix 'undefined protocol' error when opening chat from event menu. Instead of passing raw nevent as args, directly pass the parsed protocol and identifier props that ChatViewer expects. --- .../nostr/kinds/BaseEventRenderer.tsx | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/src/components/nostr/kinds/BaseEventRenderer.tsx b/src/components/nostr/kinds/BaseEventRenderer.tsx index c187f92..d9b59fc 100644 --- a/src/components/nostr/kinds/BaseEventRenderer.tsx +++ b/src/components/nostr/kinds/BaseEventRenderer.tsx @@ -197,12 +197,21 @@ export function EventMenu({ event }: { event: NostrEvent }) { if (event.kind === 1) { const seenRelaysSet = getSeenRelays(event); const relays = seenRelaysSet ? Array.from(seenRelaysSet) : []; - const nevent = nip19.neventEncode({ - id: event.id, - author: event.pubkey, - relays: relays, + + // Open chat with NIP-10 thread protocol + addWindow("chat", { + protocol: "nip-10", + identifier: { + type: "thread", + value: { + id: event.id, + relays, + author: event.pubkey, + kind: event.kind, + }, + relays, + }, }); - addWindow("chat", { args: [nevent] }); } };