Let sender know why zapping sats failed

[ed-kung]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I zapped 500 to #1198140. @felipe has a horse, and I have a gun, and yet 500 CCs were sent. Wallet logs don't show any attempt to send sats.

Screenshots

Wallet settings:

Steps To Reproduce

Not entirely sure if I can reproduce it, haven't deliberately tested on other users, nor noticed anything on other zaps (though it's possible the same issue has occurred and I just didn't notice it). I only noticed it this time because my CC balance went down a lot and I wondered what happened.

Expected behavior

Zapping someone with a horse will result in sats being sent

Logs

No response

Device information

OS: Windows
Browser: Brave (Chromium)

Additional context

No response

[huumn]

It's possible that @felipebueno's receiving wallet failed to produce a bolt11 or that it couldn't be wrapped (proxied). We don't surface those things in the sender's log - just the receiver's logs.

[ekzyis]

I looked up the wallet logs of felipe. Can confirm, their wallet is failing to create invoices.

Closing as it works as expected. This is an example where sending sats vs CCs is confusing for senders.

[ekzyis]

Or this ticket could be: should we communicate these errors to the sender, too?

[huumn]

Yes, we should communicate that an error happened to the sender

[huumn]

We can reduce general confusion by reducing specific confusions.

[ekzyis]

This is also related to having icons for sick horses and jammed guns.

[felipebueno]

@ed-kung @ekzyis @huumn I just fixed the link with my blink wallet. It looks like it's working now

@ek thank you for the heads up!