From dd85dcf2b5f9226c844ca66a1ccef0665ab4ebe2 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Mon, 19 Jan 2026 11:00:46 +0000
Subject: [PATCH] refactor: let createZapRequest collect relays from both
 authors

Remove top-level relays from NIP-53 zapConfig so createZapRequest
can automatically collect outbox relays from both:
- eventPointer.author (message author / zap recipient)
- addressPointer.pubkey (stream host)

The relay hints in the pointers are still included via the
existing logic in createZapRequest.
---
 src/lib/chat/adapters/nip-53-adapter.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/lib/chat/adapters/nip-53-adapter.ts b/src/lib/chat/adapters/nip-53-adapter.ts
index 67ae01a..b6ad479 100644
--- a/src/lib/chat/adapters/nip-53-adapter.ts
+++ b/src/lib/chat/adapters/nip-53-adapter.ts
@@ -603,12 +603,14 @@ export class Nip53Adapter extends ChatProtocolAdapter {
       relays,
     };
 
+    // Don't pass top-level relays - let createZapRequest collect outbox relays
+    // from both eventPointer.author (recipient) and addressPointer.pubkey (stream host)
+    // The relay hints in the pointers will also be included
     return {
       supported: true,
       recipientPubkey: message.author,
       eventPointer,
       addressPointer,
-      relays,
     };
   }