pull down to refresh

So maybe it's my problem. Yesterday it was working fine. My settings are correct. I'll reconfigure again to see if anything is different.
this territory is moderated
I was in a similar situation. I was all hooked up but self custody zaps weren’t working on my cell phone only. I just disconnected and reconnected from that device and now it works everywhere.
reply
I've disabled and enabled my attached wallet! Can you zap this comment just to see if it works? tanks!
reply
You asked for it!
reply
It's not working, the sats are falling into the SN wallet. Are you sure you're sending from the attached wallet? cc/ @k00b @ek
reply
54 sats \ 8 replies \ @ek 16 Oct
We need better receive logs which I’m working on
reply
6m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats 10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats 10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats 10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats 10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats 10m info wallet does not support msats so we floored 14700 msats to nearest sat 14000 msats 13m ok receives enabled 13m ok receive details updated 14m ok receives enabled 14m ok receive details updated 15m info receives disabled
reply
Oh wait! Now I think I see? @ek, does this mean there no good route between @0xbitcoiner’s node and mine? I kind of assumed all of this was going through the sn node. If not, how are you guys able to collect fees?
Lightning network is so rad!!!
reply
32 sats \ 5 replies \ @ek 16 Oct
we're fetching an invoice from the recipient, and show you a hodl invoice to our node locked to the hash from the recipient with fees added
Pretty sure.
reply