pull down to refresh
142 sats \ 18 replies \ @ek 21 Oct \ parent \ on: Olympus force closed channel with me lightning
I tried to zap @BallLightning, but the payment has been pending for minutes, so I assume they’re using Zaplocker.
If they don’t open their wallet in time (24 hours?), doesn’t the last routing node force-close the channel with their node because it’s an unresponsive node that didn’t release the preimage before the timeout?
Yeah happen to me twice, paying a zaplocker user from another wallet. I got FC in a couple of hours.
I always recommend to zaplocker users to keep their Zeus in persistent mode as much as they can, especially when they know will receive some payments to that LN address.
Persistent mode fixes this easily.
reply
Just a moment... Did you get force closed when you were paying a zaplocker user?Because my situation is the reverse (i was the receiver).
reply
Yes. But could be the way around too.
reply
I think Zeus uses some different mechanism where they hold the invoice in their nodes. I do need to claim them but I did claim them in less then an hour, so this shouldn't be the problem. Also I think the way it works is that zeus will cancel the payment themselves if the mobile node doesn't come online within a specified time, so no force close is needed.
reply
Zeus doesn’t run nodes for users, users run their own nodes.
With Zeus, you’re either using an embedded node (node in your phone) or you connect to an external node (that you also have to run yourself).
reply
Yes, their node.
reply
reply
Senders need to keep their nodes running while paying a hodl invoice, until it is settled, to avoid FCs. For embedded node users, this means leaving the ZEUS app running.
Receivers don't need to worry. Channels will not close on them even if they do not redeem their payments in the 24 hours window. They just lose access to those funds.
reply
Ah ok, doesn’t sound great that the cost of this setup is externalized to senders who aren’t even necessarily aware of this but thanks for the reply!
I won’t be zapping @BallLightning then anymore
reply
Mobile wallets should be able to ascertain this by looking at the CLTV expiry. ZEUS displays a warning for mobile users about it.
mobile only ZEUS users who want a Lightning address but don't want to use Zaplocker can set up a Cashu Lightning address
reply
On Android would it be possible for the node to turn into persistent node automatically until the invoice is settled? That would greatly reduce the problem. And also why does turning persistent mode require a restart?
Also my channel got force closed by Olympus when I had not tried to send anything. I just periodically opened it to receive zaps that suddenly started coming in from another thread. Are there any typical situations this may occur?
Yes, Olympus.
Well, first I was online soon enough.
Second, if i am offline they won't have a pending channel state change with me, that's why I think they can safely cancel. But even if I am misunderstanding something here, first point stands.
BTW I didn't know this is called zaplocker, but I remember reading how it works on zeus site i think some time ago.
reply
That node is just the forwarder, is not your node. Here is how zaplocker works https://github.com/supertestnet/zaplocker#how-it-works
I will strongly recommend to put your Zeus in persistent mode (see in options - embedded - advanced), let' s say during the day when you know you could receive some payments. During the night you could shut it down, no problem.
Persistent mode is keeping the lnd service alive in the background and can avoid these issues.
reply
Yes, not my node.
reply
TBH, we’re trying to help you but I don’t think you’re trying to understand
Anyway, maybe I’m wrong, I don’t want to spread FUD about Zeus. @evankaloudis should clarify this.
reply
WTF is this response to a post where I am actually agreeing with you?
I am trying to understand why my channel got force closed even if I can't have my full attention to this problem at the moment.
reply