Having issues with nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm this morning. In Zeus (connected to my Alby account) it shows multiple pending/unpaid invoices. I can confirm that the circled ones in the screenshot below both show up as successfully sent on the sender side, but the funds are not in my Alby account and the invoices show as unpaid. Where did the sats go? The 272 was a zap sent from Wallet of Satoshi by a user who DMd me about it, and 100 was a test transaction sent by me from Breez to my Alby address. Any idea what’s up? Alby, any help?
we had some delays this morning and the app was a bit slow. is that resolved?
which name do you mean? where do you enter the name?
You should be able to choose any name for a wallet connection in the extension.
oh noo. what happened? can we be of any help and your feedback is very appricated.
let us know if you need help.
It is recommended, yes. seems you are an early user. Back then the Alby account was connected thought the LNDHub protocol.
That one is limited and since then we use a different API which provides more features (e.g. it also shows you the lightning address in the extension)
You can simply go to "connect wallet" and then select the Alby account.
why? it's an open system you can receive with many wallets. and with NWC you can also now much easier send with many wallets.
Receiving zaps to my nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm address is failing. Still able to send zaps from my Alby NWC though. 🤔 Anyone else having issues receiving to Alby?
👀
This is recommended for all users that use the old way of adding the Alby account to the extensions. (the early users - high5 for that!)
you simply go to "Connect wallet" and choose your alby account.
then for example you'll also see the lightning address in the extension.
🚀🧡⚡️🚀🎉
join the Alby community call: https://communitycall.getalby.com/
and learn about NWC and cashu and much more.
For the friends in Berlin: https://autonomous.zone/@offline/112412332275330118
the zap will not be on the alby relay. the alby relay is solely for NWC events (here paying a bolt11 invoices. - which does not know anything about being a zap)
the recipient publishes the zap to the relays set by the client as defined in the NIP57 spec.
try the Alby relay I assume it runs more reliable for NWC.
we need to learn what are good defaults.
so far the feedback was that it helps to see the balance and there was demand for that.
but for sure it should probably handle errors better it seems. can you open an issue on github? cc nostr:npub1zk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q0gl6ef
set showBalance: false in bitcoin connect: https://github.com/getAlby/bitcoin-connect?tab=readme-ov-file#initializing-bitcoin-connect
and we run a special NWC relay that probably does not run that easily in rate limits:
wss://relay.getalby.com/v1
(we got some features coming for improved deliverability e.g. after an app was down)
If you have more feedback for https://nwc.dev/ please share 😉
ohhh, still a lot of work ahead! thanks for finding it and contributing!