Installed it, made a connection with Amethyst, though I don't have a LN channel set up, and yet I can still "Zap", confirmed in NWC as shown in the "current usage", and in Ameythst as indicated by the increased number and highlighted zap icon, but nothing was actually sent of course. (Expected an error or something but it "went through".

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

(I would tag Alby too but couldn't find them here)

nostr:note1ysd5d09dwfk8feht2gfjfhclz7f84pgz6v4m2y5qvda2e4gmc2ms7f053h

https://nostrcheck.me/media/public/nostrcheck.me_1878177119148209561689082208.webp

https://nostrcheck.me/media/public/nostrcheck.me_6201368857080751761689082237.webp

Reply to this note

Please Login to reply.

Discussion

if you kill and restart the app, is it still there? If it is, the zap event is wrong, if it is not then we have a bug in the payment error codes.

Great. So, it's just an error coding bug. It should be easy to solve.

Another issue on Alby's side / NWC on umbrel:

If I disconnect a connection, and create a new one, it save the previous permissions and historical spending in current usage. It doesn't actually make a fresh connection aside from changing the app connection pubkey.

This would also apply for a second connection, a new second would have the old seconds permissions.

I'm assuming this follows for 3rd, 4th, etc.

The code is here if you want to write an issue: https://github.com/getAlby/nostr-wallet-connect/tree/main