Replying to Avatar utxo the webmaster 🧑‍💻

I think our little raspberry pi running Umbrel wouldn't be able to handle let's say 5,000 zaps per day for over a year without blowing up.

If we did 1 sat zaps to replace "likes" I think both nodes and relays would explode.
12
Carlos 2y ago

Receiving zaps on your umbrel is a bad idea.

You expose your entire node to DoS attacks.

To initiate a zap, all it takes is one request. The node has to then create an invoice and monitor it until it's paid.

Its trivial to create a script that creates endless "zap requests" for one receiver. With every new request, there's one more invoice to monitor. Sooner or later, the node is 100% busy checking pending zaps and cannot do anything else anymore.

This is different than normal LNURL, because there, after the invoice is created, its not monitored.

Reply to this note

Please Login to reply.

Discussion

Avatar
utxo the webmaster 🧑‍💻 2y ago

LNURL generates a fresh ln invoice for each get request too, I don't think there is any difference in how it's monitored. I have an LNURL implementation I coded from scratch, it's just an endpoint where you serve a normal lightning invoice...

12
Carlos 2y ago

Yes, generates new invoice. But processing stops there.

With zaps, the receiver node has to monitor it such that, when its paid, it can emit the zap note.