When nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg sweeps funds due to a closed channel with the message "Channel closed because user manually force-closed the channel", they're not talking about me as the user, right?

Did you try zapping a zeuspay or other zaplocker invoice and close your wallet?

If you are using Mutiny I think you may need to keep your wallet open until payment confirms or any timeout occurs to reduce potential of force close.

Unfortunately, Olympus LN holds invoices until zeuspay users are online and timeouts can be a day. This is why I dont zap zeuspay users. Their LSP creates too much risk and is a bad actor.

Reply to this note

Please Login to reply.

Discussion

Yeah that's the message LDK gives for the reason but it essentially is because of an in flight payment that the user didn't check back on in time. So your wallet force closes asap when you open it after these timeouts have already passed.

OK thanks to both of you for taking the time to explain! I'd zap, but first I gotta pay some on chain fees 😅

Hey nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg one more thing, maybe related: I've had a pending zap payment for 2 months, is this a known issue? Just want to check before I restore my wallet to try and get rid of it. I can submit a bug report to Github if this isn't a common issue.

Do you switch wallets (or did so at the time)? That happens. If it's been longer than a few days then it probably failed on a different device and didn't update on this one. Right now the work around is to just restore from seed words, we don't have individual deletes on these right now.

Yeah I got a new phone and changed my wallets around. Thanks for the help today.