Avatar
bumi
330fb1431ff9d8c250706bbcdc016d5495a3f744e047a408173e92ae7ee42dac
working on getalby.com - a browser extension with lightning and Nostr support
Replying to Avatar saunter

https://m.primal.net/Haat.mp4 🤔 #nostrdesign #buildinpublic

that’s an awesome idea

Replying to Avatar Jingles

😨

you do not loose sats. you might need to contact support, but no sats are lost!

invoices are always 1 to 1 (which is why lnurl and such has been invented)

an invoice paid from alby to alby is not blocked on the LN network and could be pid by an external wallet once again (only once). but because the invoice is actually already paid the amount is not automatically visible in this case.

I still wonder what’s your use case there

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

awesome! thanks for the detailed, great analysis which is mostly correct!

The invoice is not rejected on the lightning level which means another ln wallet can still pay it.

but what is your use cases there? why would you give the same invoice to multiple people? an invoice is always a 1-1 relationship.

can you send the details to support@getalby.com it will be taken care of there to make sure the second transaction shows up.

Yes, this is currently an issue. If paid with Alby LND still does accept an invoice payment through the network.

No money is lost, but the second transaction is not credited.

It's a support case at this point.

My nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm ext is completely dead rn. It’s not just the wallet this time. Even the Nostr nip-07 functionality is not working. Anyone else having problems?

what issue did you see?

the extension is a client side app. if you see an error, please report to make it better (best on github)

yeah, that's a good practice. but we also work on solutions there and NWC is at its core.

It's still a few more weeks I think, but we'll be looking for beta testers 😉

this is our official status page: https://alby.instatus.com/

sorry for the downtime last night.

yes, sadly we had some downtime last night caused by issues in our data centers. But everything is up by now.

you can always follow the system status here: https://alby.instatus.com/

Sorry for the interruption. We sadly had some too long downtime initially caused by a data center issue with our hoster.

Does everything work for you again?

thanks for the explanation, that's super helpful!

can you open https://relay.getalby.com/v1 ? (the website is completely separate from that.)

could you try https://bitcoin-connect.com/ works for you? (and if you see errors what errors do you see in the console?)

Replying to Avatar Dr. Hax

I guess it's time to look for alternatives to nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm. Having a lightning wallet that doesn't work reliably when combined with privacy software like Tor is not useful. I can't zap anyone!

Anyone know of a lightning provider that is usable ny mere mortals (i.e. people who aren't lightning developers) and treats privacy advocates with respect?

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z what do we do here?

I fear this is more Tor being unreliable or something? do you have an idea how we can better debug these Tor issues?

people cursing like that get charged double. ;)

if you don’t value our services your always free to use anything else.

that’s the beauty of open protocols.

what's your one-sentence ELI5 answer to:

"ecash is just a different from of custody"

?