Nostr Web Client

Every time I try to zap a note, I’m getting “error fetching Lightning invoice. Any troubleshooting tips?

I promised zaps and now I’m having trouble delivering 🤦‍♂️😞

I’ll try resetting my NWC to Alby in the morning. If anyone can recommend other ideas while I sleep, it would be appreciated 🙏

Using nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 but not sure if it’s a client issue… it’s happening on every user though so I don’t think it’s the receiving wallet. Cc nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x

#asknostr

nostr:note1u7gqswk3srtnh4ndnw04ru6guwg8u4er9km8xr2e8c0hdq55lp4sd4l5lj

Reply to this note

Please Login to reply.

Discussion

zach 1y ago

Has happened to me too here and there. Somewhat more recently (could be recency bias though)

I usually just re-press it until it works or I give up, whichever comes first.

Tony 1y ago

Same here. Are you using Alby Hub? Good practice will be opening another channel to some well connected node. At least that’s what I’m planning to do.

zach 1y ago

Yes, good thinking. I do need more channels!

bumi 1y ago

actually it depends (as always)…

depending on the usecase it is also not too good to spread funds across too many channels.

the LSPs should be very well connected.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

my heuristic is that channels should be 1000000 minimum and one should have a minimum of 2 of them, one inbound, the other outbound, it really depends on how much money goes in and out on a monthly basis but you don't have to keep them even much better than 25% filled at any given time, but it's really worth having that extra capacity in case some people decide to send you or you need to receive more than 100ksat several times before you are moving it elsewhere

Tony 1y ago

Totally. My point is that for the sake of redundancy 2 channels make sense.

I do in fact run into troubles of not being able to zap some people from the first try. https://v.nostr.build/lmMDIEvenSF6LGcR.mp4

boston wine 1y ago

Hey, thanks for replying. I’m actually not using my Hub account with this nsec - it’s a simple “legacy” custodial Alby account

What’s odd is that the error only appears when I try to pay the invoice as “public” - when I set it to “private” then it seems to work

Tony 1y ago

Super odd. Way above my poor technical knowledge 😅

Dan Wedge 1y ago

I am going to hail nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 here I think this might be on Damus side. I am using WoS and find the same issue maybe the last 2 weeks ish

Tony 1y ago

boston wine 1y ago

🤣🤣🤣

boston wine 1y ago

Interesting - why is not as good to have your Alby hub funds in multiple channels? Something to do with re-combining funds to make larger payments?

(PS - DM’d you about the larger payment issue if you have a chance to look into it)

bumi 1y ago

who do you try to zap?

this is an error on the recipient side.

dvo 1y ago

did you ever get this working? I’m using damus with alby hub and it works amazingly well with no issues 🍣

boston wine 1y ago

🍣😂🤙

Seems to be working now. My Hub is separate - just custodial with the npub