Hmm. I’m not sure if there is a good way to store this securely since it has to all be read by the server based on a trigger of a “like” and not some explicit action from the zapper (I.e. making an API call and decrypting the encrypted string to make the payment). Only solution I can think of is running a “personal” zap agent on your computer for yourself that performs the same function. You’d still need to protect your nwc info but at least you’d be responsible for yourself.

Replies (2)

I didn’t say it was an easy problem, so it is hard. If it’s a serious service, I would take a look at what Asinq did with their routing node. They definitely put in a lot of thought into it 🐶🐾🫡