having issue one tap zapping to profiles receiving with #[0]
Discussion
Yeah I’m done w alby
I like their extension first to support nostr, maybe its one point of failure but easier to trust a signing extension that has a financial reputation to uphold & I'm successfully zapping out and splitting to client devs. I use #[4]‘s lntipbot as my receiving wallet and really enjoy that.
What is not working for you nostr:npub1g0xdhjc7fhlhu00292gms5w2pc302r3u2cpkfgftvjuvvkreyncqvnywzf ?
won't let me zap #[2] but also won't let me zap #[1] themselves... Other zaps are leaving alby and showing to other receiving addy’s
on no. Let's have a look. In which app are you zapping?
Damus, 1.5(4) & 1.5(3) still same issue the morn... I'm tipping out of my alby wallet just fine, but zaps to #[4] & #[2] accounts won't even generate a temporary zap. I did try on snort just now, and that did work so 🤷♀️ maybe not an alby issue. Brb gonna check a 1.4 build.
in 1.4 builds it still says “error fetching ln invoice” but at least will let me get to the pop up screen. Glad it works else where tho.
Do you try to send a zap in Damus with Zeus wallet? I have an Alby account connected to Zeus and the transaction was successful to Alby lightning addresses and and others.
“error fetching ln invoice” --> which Nostr profile did you try to zap?
yeah In damus my sending wallet is wallet connect with alby, no zeus involved. I'm still experiencing the error fetch with #[2] with #[4] & yourself.
I also just disconnected the wallet connect... All other receiving wallets I try offer me an lnbc link... But damus seems to have an issue still fetching the invoice from an alby reciver
