reply on: Olympus force closed channel with me \ stacker news ~lightning

pull down to refresh

110 sats \ 18 replies \ @DarthCoin 20h \ on: Olympus force closed channel with me lightning

You didn't mention when did you purchase it. maybe the lease period expired and you didn't notice it.

What can cause a force close of a channel (before expiring the lease):

your Zeus mobile node had a bad state of the channels.db, data corrupted, no more space on your device...
you've tried to send a payment to a HOLD invoice that got too much time pending HTLC on the path, usually when destination is not online for long time.
your node is not syncing well (mostly because is behind Tor or a bad VPN) and trying to restart several times the service it could generate some mess into communicating your node status to the peer.
see more causes that can trigger force closures here: #658770

Always take a look into your lnd logs and also in the app logs.

To avoid data corruption in channels.db, I would suggest to do periodically a compactation of the database (see options - embedded ndoe - troubleshooting) and also if you do not use it very often, delete neutrino files and resync with new ones.

This could wipe all bad status data and re-write fresh ones.

Also Zeus Docs are quite explanatory for these cases: https://docs.zeusln.app/for-users/embedded-node/faq/

100 sats \ 17 replies \ @BallLightning OP 19h

My lease should have expired after 5 months, so this is not the problem.

I don't know if my zeus was in bad case. It hasn't crashed or anything like that so if this is the case it is a serious bug on Zeus's side.

I haven't tried paying hodl invoices or any invoices. I did receive some sats from Stacker news with the Zeus built in functionality and the sats were received without a problem (this was earlier today).

My connection is very good right now (and this shouldn't cause such problems if coded by good developers anyway).

I can't find anything in the logs. I think the logs don't keep everything so I may have missed the relevant lines.

I will read the materials you provided later, but this is unexpected and considering I have paid money for this channel, (6 month channels are not cheap), i would advise people to have it in mind and maybe not use this functionality for now.

I also had a force close from megalith LSP, but I expected to not have problems with Zeus own infrastructure. The megalith LSP channel didn't allow me to send anything, no matter the fee, which was quite strange. But now I think Zeus wallet itself has serious problems...

182 sats \ 15 replies \ @evankaloudis 19h

Reach out to support and we'll investigate and get you a replacement channel.

142 sats \ 14 replies \ @ek 18h

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?

222 sats \ 2 replies \ @DarthCoin 18h

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.

0 sats \ 1 reply \ @BallLightning OP 17h

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).

0 sats \ 0 replies \ @DarthCoin 17h

Yes. But could be the way around too.

0 sats \ 10 replies \ @BallLightning OP 18h

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.

0 sats \ 9 replies \ @ek 18h

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).

0 sats \ 8 replies \ @BallLightning OP 18h

Yes, their node.

0 sats \ 1 reply \ @ek 18h

Oh I guess you mean Olympus

That node is “cancelling the payment” by closing your channel if you don’t come online afaik

0 sats \ 0 replies \ @BallLightning OP 18h

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 on another page

0 sats \ 5 replies \ @DarthCoin 18h

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.