There was only the "Close channel" button. Zero additional setup was possible while performing the operation.
what feerate does your transaction pay? This should also be reported to whatever LSP you used, as their node's money is also stuck (assuming it was a cooperative closure) and their node should not have accepted a very low closing fee
though I wonder...since you said your money could be stuck for 14 days, that is the standard "force closure" period. Are you sure it's stuck due to fees and not do to the timelock delay on force closures?
reply
This is the info from the wallet…
reply
Seems like your money is stuck due to a force closure, not because your tx pays a low fee.
Your wallet and your counterparty's wallet couldn't agree on what fee to pay to close the channel. Your wallet thought fees were pretty high so you wanted to pay a high fee to get your transaction confirmed; their wallet thought fees were pretty low and they didn't want to pay a high fee and potentially collect less money than they think is due to them.
When your wallet can't come to consensus with its counterparty, it ignores them and withdraws your money using its presigned force closure transaction. But that also means "one of you might be misbehaving," so the force closure transactions are timelocked to give your counterparty time to prove whether you've done anything malicious. You haven't, so you'll be fine, but you do have to wait while an up-to-2-week timer runs out.
This is an inherent difficulty with lightning: you can't do "whatever you want" with your lightning utxos because they are "shared" utxos. Your counterparty has half of the keys, so anything you want to do with them, they have to agree on it. In this case, you couldn't agree on what to do with that utxo "right now," so you have to use whatever you last agreed on -- and lightning always ensures the "last" thing you agreed on is a unilateral withdrawal transaction (so you'll definitely get your money out), but it's timelocked.
reply
Thank you kindly for thorough explanation πŸ™‡πŸ»β€β™‚οΈπŸ™πŸ»
reply
you're very welcome
reply
Yeah, I noticed this as well a while back. I should have posted about it.
reply