nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 First major issue(s) with your wallet. Trying to provide some feedback. I had a large channel w you guys force closed, and it has been pending for 5 days. The sats I had show up in the on chain portion but are still pending 5 days later despite a confirmed tx already having been executed. Secondly, I had another open channel with another node and had plenty of inbound liquidity. I tried to send a Lightning transaction to my wallet via that channel, but the app forced a 10k sat fee on me and opened a new a channel. Why would that happen when there is plenty of inbound liquidity from another channel?

Reply to this note

Please Login to reply.

Discussion

Force closes fees can be on hold for up to 14 days after the force close tx is mined, this isn't anything to do with Zeus and is just how lightning works. Rest assured your funds are safe :)

Less concerned about this issue. Understood force closures and time to settle happen. It’s the channel issue that is a real problem.

Possible there was no possible route to the node you were trying to make a payment to through your channel, however I agree that the UX should communicate this and not just open another channel automatically if that's what happened.

It’s the ACINQ node. I’d be shocked if there wasn’t a route.

FWIW, I experienced your second issue (or something similar) when I unknowingly tried to receive before my existing channel was ready (i.e. it was still in the offline state).

I think it would be nice to have a warning in this scenario to let the user know to wait until any existing channel comes online in order to receive, instead of taking 10K sats and opening another channel.

It did pop up at the top, but I thought it was more of a warning if I didn’t have sufficient inbound liquidity, which I did, it would then open a new channel. Now I’m trying to send another Lightning transaction and it wants to open a new channel again.

Ah ok. Maybe I missed it. 😄

Keep us posted then. Sounds like a potential issue with non-Olympus channels.

Check my back and forth with them. Gotta disable the LSP option.

Got it. Thanks..🤙

I have tried again to send over Lightning into a channel I have open, but the app is trying to force me to open a new channel with the 10k fee again. Maybe I am missing something here, but this should not be happening.

1. Sounds like your wallet is out of sync w the chain. Go to Neutrino peer settings and make sure your peers have ping times under 200ms or remove them. Then restart the app. Your balance should be reflected accurately. That being said, if it’s a force close it has to have the timelock expired if you were the initiator.

2. Invoice wrapping only works if you’re using it with the LSP. If you don’t want to use the LSP disable the toggle, and you can receive payments without being charged for new channels- but you are responsible for the channel management

Number 2 solved the issue. Thank you. Not sure if you could have that option pop when someone is trying to send in and doesn’t want to have it open a new channel.

We’ll give a thought to the UX. You can also disable it under Settings fwiw

I have now. Ty.

How do you find the Neutrino peer settings? I can’t seem to find those.

Embedded Node > Peers

Got it. Ty

Is there a way to have onion address peers?

Actually I am not sure if there are neutrino TOR peers..

For now you’d have to run a Tor networking app alongside it like Orbot