I think the main issue is the blocking nature on anything that does not use the default zap, no? So if you comment, post or even just select a custom amount, the UI currently blocks until the payment failed or was successful.

If that's true, the toast isn't the problem afaict. As @k00b mentioned, it only exists so one can cancel pending payments.

> In the nostr apps that use NWC the status of the lightning icon just updates...

You mean like showing a spinner instead of the lightning icon? Mhh, I see. Maybe we can do that instead of toasts and clicking the spinner would cancel the action. But that's a bigger lift, not sure if it's worth it if the toast is not the real problem.

They accidentally zapped and want to abort the payment. You've expressed wanting to abort custodial zaps in the past (which we are also working on). Have your feelings around that changed or did you have something else in mind?

I guess my question is why is the toast even needed in the success case? Why should user care?
In the nostr apps that use NWC the status of the lightning icon just updates... 

nout

We're going to house an abort button on the toast eventually, but should probably make it lower contrast than it currently is.

k00b

SN release: NWC & LNBits for sending, LND for autowithdraw, NSFW labels, & more

Super cool! Yeah, I'd say it would be better to switch to optimistic UX - just make it look like it's been zapped immediately and only pop up any dialog when the payment actually fails (it could also just be a SN notification).