Hey Alby Team.
I noticed a weird situation.
I have generate an alby account with balance A, and I have another OneKey account with balance B.
I generate an invoice of n sats by alby account. My friend with another alby account having balance C pay this invoice. and then i use OneKey pay for that invocie again. Both payment is successful, but my =alby account can only recieve first payment. and my final balance is alby : A+n, my friend: C-n, Onekey B-n.
So there is n sats just gone with the wind?
nostr:npub1zk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q0gl6ef nostr:npub1q5sah9f3p9kl7uqdeaqskqwmg74ktxx70e0093dzh4lpzcp3t0mqzxky65 nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x
I'm gonna make a guess here because I've encountered the same issue when building things on LN.
It sounds like a subtle issue with Lightning implementatios: internal payments have to be settled internally in a separate database and not in the lightning node itself (LND doesn't support self payments, afaik CLN now does).
When the second payment is made through the real LN, the invoice is picked up by the node but the Alby backend already settled the invoice.
yeah see my another post of my assumption
I also tested other lightning wallet. WoS and blink is safe, they handle this situation specifically
OneKey wallet also has same issue.
Alby support handle this specifically. Not at software level.
nostr:note15gv0azs7tyw86cyee84eywfthtnn52lvaedl9yg2m8hey0aj604qnz9ypx
