Unknown Zap Invoice #160

Closed
opened 2024-06-05 11:58:11 +00:00 by moosesnWoop · 3 comments

I had an issue yesterday sending zaps to TheGrinder on his channel. It was a confirmed send on my end to the QR code, but he never recieved it. First time it's happened, thankfully it was a smaller zap amount.

I'm using Wallet of Satoshi and haven't had an issue with zapping so far, either topping up or zapping a channel. This is the first time I sent a zap + message which confirmed, but did not appear in the chat window or TheGrinder's wallet.

So not sure if the QR swapped to something else - but the 69 sats have been debited.

I had an issue yesterday sending zaps to TheGrinder on his channel. It was a confirmed send on my end to the QR code, but he never recieved it. First time it's happened, thankfully it was a smaller zap amount. I'm using Wallet of Satoshi and haven't had an issue with zapping so far, either topping up or zapping a channel. This is the first time I sent a zap + message which confirmed, but did not appear in the chat window or TheGrinder's wallet. So not sure if the QR swapped to something else - but the 69 sats have been debited.
Owner

No a zap.stream issue, all zaps are sent directly to the streamers account, probably an issue on the receiving wallet system

No a zap.stream issue, all zaps are sent directly to the streamers account, probably an issue on the receiving wallet system
Contributor

No a zap.stream issue, all zaps are sent directly to the streamers account, probably an issue on the receiving wallet system

I was thinking the same. either inbound liquidity on Alby or outbound on @moosesnWoop WoS. I've checked again and I have not received the 69 sats with a tx message. This has to be on WoS's end.

> No a zap.stream issue, all zaps are sent directly to the streamers account, probably an issue on the receiving wallet system I was thinking the same. either inbound liquidity on Alby or outbound on @moosesnWoop WoS. I've checked again and I have not received the 69 sats with a tx message. This has to be on WoS's end.
Contributor

@moosesnWoop I just took another look and I now see the 69 sats below Eitoon's 21 sats zap. My assumption would be that this was settled by either wallet with a huge delay (for whatever reason).

@moosesnWoop I just took another look and I now see the 69 sats below Eitoon's 21 sats zap. My assumption would be that this was settled by either wallet with a huge delay (for whatever reason).
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Kieran/zap.stream#160
No description provided.