Force closes have two transactions. The second, a sweep to your wallet, probably hasn’t occurred yet.
Going to reach out here, and message on the main as necessary; I used a Bitcoin transaction acceleration service to confirm a high-value nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 force channel closure (via embedded node) that's been sitting in the mempool since mid-November of last year.
It was confirmed not too long ago, but no funds have been returned to my on-chain wallet; I have restored my wallet twice now, and the second instance (briefly) had the channel under the "Pending Channels" section which now shows nothing.
Could you assist with this, Evan?
Discussion
How long would that take after a minimum of three confirmations? As I'm typing this reply, it's at five now.
It should happen pretty quickly, but your wallet needs to be open to trigger it
There's no Lightning channels available to take advantage, but would Persistent LND keep it open to receive on-chain sweeps?
Yes, that should work
Checked up on Mempool in case locktime was still applicable, and attempted restoring on-chain wallet access using my seed on both Blue Wallet and Blixt.
No dice, along with blockchain rescanning in ZEUS failing.
None of those things will work if it hasn’t been swept yet. Funds need to be pulled into your main wallet w a sweep tx initiated by LND
I'll message you the transaction page on mempool.space to dial down what needs to be done on my part (aside from waiting, lol).
Thank you for helping out, mind you. I know ZEUS can't account for what LND does wrong.
Sent from here, not sure whether or not your client supports gift wrapped messages lol.