A peer force-closed a channel. I guess that the fee is low as the closing transaction doesn't show up in the mempool. How do I CPFP one of these? I can't find the details of the transaction though I was able to copy the transaction hash from lndg.
https://mempool.space/tx/94bd944e96ec7e1c4541ad0a13d0278f04399d74ad1fa8572ec45d3c49d35c56
You need to find an output that you control to spend it with a higher fee rate.
I tried to find the Tx in bitaroo's mempool which has 1GB of unconfirmed transactions but I couldn't see it.
I'm not sure where to go from here.
Can you see the pending channel close on your node? How is the channel being shown in RTL?
Not visible in the mempool. I can't see what my output is from the force-close transaction. Maybe this could be extracted from the channel.backup? I haven't been able to do it. If I could find that, then maybe I could form a CPFP. That may not even work if the child transaction is being rejected from the mempool...
Thunderhub lists the channel as pending but shows no closing transaction hash. LNDG, however, does show the closing transaction hash:
94bd944e96ec7e1c4541ad0a13d0278f04399d74ad1fa8572ec45d3c49d35c56
Parent transaction but yeah - i had a similar thought. How can you create a valid transaction using the output on an unconfirmed transaction that doesn't exist?
You can't see any remanants of the channel in RTL?
Here's everything that I've got on it:
"waiting_close_channels": [
{
"channel": {
"remote_node_pub": "0249ab25ebc69a4f71d1c3019c5c653e8b2a84ad3916c899139fb3e7825858b3e1",
"channel_point": "564214bd21c41a9713668771bd94dc7e3622f32d797f87324ad5f897f4e66943:1",
"capacity": "4000000",
"local_balance": "2128951",
"remote_balance": "1020222",
"local_chan_reserve_sat": "40000",
"remote_chan_reserve_sat": "40000",
"initiator": "INITIATOR_LOCAL",
"commitment_type": "ANCHORS",
"num_forwarding_packages": "138",
"chan_status_flags": "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator",
"private": false
},
"limbo_balance": "2128951",
"commitments": {
"local_txid": "94bd944e96ec7e1c4541ad0a13d0278f04399d74ad1fa8572ec45d3c49d35c56",
"remote_txid": "0375d3a4f459182c1952f2dce5d58f6cba8e2c16c0b5e22317e39e1a736be496",
"remote_pending_txid": "06ae6c1acae708440b2f391cd81267380d3241c9b9edb8ec0a7ea3d04c0f5213",
"local_commit_fee_sat": "7775",
"remote_commit_fee_sat": "8590",
"remote_pending_commit_fee_sat": "0"
},
"closing_txid": "94bd944e96ec7e1c4541ad0a13d0278f04399d74ad1fa8572ec45d3c49d35c56"
}
]
This is my channel partner. I haven't been able to reach him yet.
When did you initiate the forced close?
You know that there's a time lock delay for a forced close to give the other node a chance to respond to the close request?
The default is 144 blocks (24hrs).
I'm not sure if the node waits this time before broadcasting the close Tx.
This is a super interesting problem.
I feel like I'm way over my head with it.
Any thoughts nostr:npub1ftd5lukuw2alrak6r87ppyqg5fgp8jpheacjq95h97kszkce2yls5dv5jq?
