Sherry on Nostr: Alby here is my analysis (assumption) And I think it won’t be too difficult for ...
Alby (npub1get…0nfm) 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
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?
Roland (npub1zk6…l6ef) Moritz (npub1q5s…ky65) bumi (npub1xv8…lk3x)
Published at
2024-01-30 02:39:31Event JSON
{
"id": "a218fe8a1e591c7d6099c9eb92392bbae73a2becee5bf2910ad9ef923fb2d3ea",
"pubkey": "cc8d072efdcc676fcbac14f6cd6825edc3576e55eb786a2a975ee034a6a026cb",
"created_at": 1706582371,
"kind": 1,
"tags": [
[
"q",
"2c90b90478b6266b5521bae603ab5f8fa1865b4774cb7274fc73d37ea2f66cd9"
],
[
"p",
"cc8d072efdcc676fcbac14f6cd6825edc3576e55eb786a2a975ee034a6a026cb"
],
[
"p",
"4657dfe8965be8980a93072bcfb5e59a65124406db0f819215ee78ba47934b3e"
]
],
"content": "nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm \nhere is my analysis (assumption) \nAnd I think it won’t be too difficult for alby to fix it. \n\n1. 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\n\n2. 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). \n\n3. However, that invoice is not revoked, even it’s actually used and Alby system is aware about this fact. \n\n4.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. \n\n5. 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",
"sig": "2ade2e9822904a7b66cdd8c78b3dd71b1c76689a79b8938b9e14565260ccee1db6799b5ac99c31733f8cc7ebedd6ab7395247b1f72a25ce7dbb2a7cb7f96e559"
}
