Resolving Waiting Close and Unconfirmed Transactions #8006
-
BackgroundI currently have this guide for Umbrel users, any feedback appreciated Trying to follow the LND guide I'm confused on which portion should be used and in each circumstance as per the LND doc, Does bumpfee for CPFP work in most scenarios on channel closures? and it must be this kind of command?
Or more something like this?
Or can I confirm the recommended command step-by-step you should use to speed up the sat per byte on the closings showing unconfirmed? I'd like to explain this easier and separate what is and isn't possible, For waiting close and unconfirmed LND closings, should we bump fee or use the --start_height command? How can we tell for sure when closing between us and the peer if RBF is enabled and what to use? How can we tell if that user is a CLN peer? Thanks for input Your environment
Steps to reproduceClosing all channels in LND Expected behaviourAll funds returning onchain Actual behaviourChannels are stuck waiting close for longer than 1 week |
Beta Was this translation helpful? Give feedback.
Replies: 16 comments 5 replies
-
|
Here is the pending's I currently have waiting to close. any of them with Tor address do not have a unconfirmed transaction yet in the pool. The clearnet nodes do have unconfirmed. I want to speed those up as they have been set to 10sat/vb and will never clear. |
Beta Was this translation helpful? Give feedback.
-
|
I have tried to bump close fee using the following command against the channelpoint of the channel open, it didnt return an error but I have not seen anything happen either. |
Beta Was this translation helpful? Give feedback.
-
|
You don't want to bump the channel outpoint, you want to bump the anchor outpoint |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply @alexbosworth, Myself and others were having trouble with this, is it true from reference:
And I couldn't find an example of the anchor outpoint command? We are not able to use it in this scenario @xgfreon shared above? What would you recommend? Your input is really appreciated - want to learn and then help others having issues after switching setups/closures too |
Beta Was this translation helpful? Give feedback.
-
|
The anchor output you can see is the 330 small outputs on the pending unconfirmed transaction Bump fee can spend this outpoint into a child tx and then if that tx is a high fee it pays for the parent transaction to confirm, that's CPFP |
Beta Was this translation helpful? Give feedback.
-
|
@alexbosworth Forgive me if I'm not yet grasping, I grab his anchor outpoint from the mempool, for this tx as an example? and it would be
Where does one grab that ? tysm |
Beta Was this translation helpful? Give feedback.
-
|
The close for that tx is The anchors on that are index 0 and 1 You can see it is already being CPFP'ed via the index 1 |
Beta Was this translation helpful? Give feedback.
-
|
😬⚡ I haven't been able to find where you got this from
|
Beta Was this translation helpful? Give feedback.
-
|
That is the id of the unconfirmed tx that spends the channel outpoint, the commitment transaction |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah my understanding is we can bump but we can't CPFP unless you also own the outputs to the TX... |
Beta Was this translation helpful? Give feedback.
-
|
@alexbosworth if you look at another of my pending channels from above, in Lnd-g It says channel closed, however when i goto the mempool and look for a close like https://mempool.space/tx/fe5801b134c3b5c54a8597a630f98bf9ff68418ece0a66b9d4a2022bac598f91 I have this issue for any of my channels that were TOR only channels. I have tried to send a force close using Chantools but it tells me the address is not reachable, I have only been successful using chantools on clearnode ip's only. The node clearly shows online from amboss or 1ML. |
Beta Was this translation helpful? Give feedback.
-
|
@xgfreon maybe you can contact them their twitter and Telegram are linked their to initiate the cooperative close? |
Beta Was this translation helpful? Give feedback.
-
|
I don't have enough info from what you posted but if you want to close a channel and you still have the channel state you can try to coop close or force close the channel If a force close gets stuck in the mempool and it's an anchor channel and the parent is above the minimum relay fee you can fee bump the anchor |
Beta Was this translation helpful? Give feedback.
-
|
Moving this issue to a discussion thread, as there is nothing to fix here. |
Beta Was this translation helpful? Give feedback.
-
|
I'm in the same situation but my channel is not anchor, it's "commitment_type": "STATIC_REMOTE_KEY". |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately with the If you can communicate with your peer and they are willing to cooperate, you could use the zombie recovery flow described here: https://github.com/lightninglabs/chantools/blob/master/doc/zombierecovery.md |
Beta Was this translation helpful? Give feedback.
-
|
That's a pitty. I don't even know why this channel (and maybe other) are in this type and not anchor, are they just too old? How to prevent opening channel with STATIC_REMOTE_KEY in the future? I contacted the peer already, but the procedure seams extremely complicated. We will see what is possible. Remain an external accelerator service but I don't know which one to use, mempool space one is on waiting list only, I don't know other that are trustfull. |
Beta Was this translation helpful? Give feedback.
-
|
Not all implementations supported anchor channels until recently. But if you open new channels between |
Beta Was this translation helpful? Give feedback.
-
|
as @guggero states his zombie tool links you with the missing peer and is from my understanding, @nmfretz iirc the new flow you developed, will more easily let @ElucGeek see any channel had he not seen them reliably on the opt-in and friendly UI if he is not not updated?-- albiet, may be unrelated to that lengthy tree of possible outcomes here in the diagram? under "Channel recovery scenario" |
Beta Was this translation helpful? Give feedback.
-
|
afaik @ElucGeek just run pending channels command and hope your peer accepts your close broadcast if they are around right? perhaps i can still try to iron that out hopefully there is some kind of resolution for this like a remotesweep after identifying if the peer is eclair or something, or something with a user friendly UI :) |
Beta Was this translation helpful? Give feedback.
The anchor output you can see is the 330 small outputs on the pending unconfirmed transaction
Bump fee can spend this outpoint into a child tx and then if that tx is a high fee it pays for the parent transaction to confirm, that's CPFP