I'm missing out on the whole #zapathon phenomena because doing it the right way is just too complicated.

I feel really uncomfortable promoting Alby or WoS with my profile and the btcpayserver plugin requires me to set the lightning address to match the nip05 and I have to put my nostr private key into the btcpayserver?

nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg and Shaumian mint devs wouldn't this be something to tap into? Zap by sending encrypted tokens to npub instead of LN addresses? The nostr identity could then acknowledge the receipt with a zap message. No need to configure nip05.

Reply to this note

Please Login to reply.

Discussion

No need for the private key in the server

The zap is emitted by the LN node, isn't it? Or the nostr client needs to get a notification from LN node to emit the zap. Either way, the btcpayserver nostr plugin asks for my nostr npriv

You may have an older version. New key should be generated for zaps

I am by no means a dev but this 👆🏻 sounds smart.