Replying to Avatar Sherry

nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm

here is my analysis (assumption)

And I think it won’t be too difficult for alby to fix it.

1. When the payee requested to receive a payment, he uses the Web UI to create an invoice and Alby call it’s LND, record this in DB and send to user

2. If the payee sends this invoice to the payer, which happens to be another Alby user, Alby only record this operation on DB and update both sides balances (i.e. deduct from payer and credit to payee).

3. However, that invoice is not revoked, even it’s actually used and Alby system is aware about this fact.

4.Then someone from an external wallet tried to pay this invoice. Since it’s not technically used, LND will accept this payment and Alby LND node still receive sats.

5. However, when Alby try to look up payee in internal db but found this invoice “has been used internally”. Some errors throw, and balances not updated nostr:note19jgtjprckcnxk4fphtnq826l37scvk68wn9hya8uw0fhaghkdnvsu0t2qu

I was just going to suggest this might be what's happening when you were able to replicate with WoS as well. It's something we explicitly had to guard against in nostr:npub13ljnkd633c7maxatymv3y2fqq8vt3qk7j3tt0vytv90eztwgha9qmfcfhw

Reply to this note

Please Login to reply.

Discussion

Oh cool!

Thank you! I believe This will be super useful if alby starting fix it . I will add it to my lnd too lol

I think wallet of Satoshi guard it too. When invoice generated by wos duplicated payment is not allowed