pull down to refresh
Conceivably, this could be combined with an invoice replay attack in niche situations where the invoice is being presented by a 3rd party, but either the destination is validated, or the skimmer wants to be discrete.
If you're using an LNURL bridge for example, this would be reason to have a short TTL on your invoices.
Thanks for the comment, but im kinda sad that i barely understood what you are saying but i upvoted anyway
I've done it when I get a payment that takes too long. I test out new lightning wallets all the time, and not all of them are very reliable. So when I try to pay an invoice, it often gets "stuck" for several minutes trying to pay without either failing or succeeding -- just "pending." When that happens I usually switch to a different wallet and try to pay the same invoice with that one. In other words, without making a mistake, I try to pay the same invoice twice. I did not consider that I can lose sats doing this but now I will take that into consideration.
Paying an invoice a second time has to be a mistake most of the time. If thats the case you made a tool to steal sats from people who make this mistake? What im missing