got it, I don't have experience in that scenario, but I think if you receive a list of relays you could create a pool with those relays and publish to all of them, that pool would be temporary I guess but I think it handles the connections for you.
I don't think that will work for Zap Receipts. For these receipts, the NWC provider must dynamically connect to an send messages the relays that are specified in the inbound message ... see here: https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-a-zap-request-event .... so we can't know in advance which relays we're supposed to connect to... we need to dynamically connect to the relays depending on what the zap recipient specifies...
Discussion
No replies yet.