pull down to refresh

Here are pics I took a minute ago from my notifications page and my wallet logs. Why is there only one error showing in the wallet logs if I've got this many failed zaps? Is there something I'm missing?

(Also, I'm once again begging for a good failover to CCs or even my SN wallet for failed zaps.)

121 sats \ 0 replies \ @ek 27 Jul

It might be because the receiver wasn’t even able to return an invoice so your wallet didn’t even start paying. Sender wallet logs only start when a payment attempt starts.

That’s confusing, maybe we can change that.

But also need to confirm if that’s what you’re seeing.

reply

This is kinda weird. I've heard Coinos messing up incoming payments, but the strange thing is I got the 25 in CCs, but no sign of the 70. No notification, and it's not even showing up in the stats. cc/ @ek

@Aardvark, did you zap this comment?

#1056971

reply

withdraw sats to coinos address works. Just tried it.

reply

Just tryna figure out the logs. Those two that failed, am I s'posed to get them as CC's? cc/ @k00b

reply
21 sats \ 3 replies \ @k00b 27 Jul

Something odd is going on with coinos (they changed something in their interpretation of the spec and we don't know what): https://github.com/stackernews/stacker.news/issues/2342

reply

deleted by author

reply
30 sats \ 1 reply \ @k00b 27 Jul

This is an NWC thing afaik ... folks are zapping you with a coinos NWC that is broken on coinos' side (other nwc "providers" works fine).

reply

My bad, that comment wasn't for you. I meant for it to be a follow-up to my own comment on this post. #1057083

reply

Yeah, I noticed that too. Failed zaps dont always show in the logs could be a backend sync issue? A fallback to SN wallet would be a solid fix.