It’s not my app. Screenshot is from nostrudel. Cc @hzrd149
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)
Discussion
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
try the Alby relay I assume it runs more reliable for NWC.
K let me test
payment went through, but zap is not showing on the note. i think maybe cause the clients i'm using are not querying the alby relay for the zap receipts. i checked damus and primal. the alby relay is not on my relay list so that could be the problem. i don't think many people have the alby relay on their relay list.
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.
I've fixed the issues and added a PR for Nostrudel CC nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr 🙏
merged 👍