[bug]: RBF Confirmed, Channel not open then closed tx not broadcast

[jiraiyax]

Background

I have been open channel with PSBT. I signed transaction using electrum then broadcast by lnd. After that I do bump fee by using electrum and transaction has confirmed but channel do not open. After all I do force close with "lncli closechannel -force" but closing tx not broadcast. What can I do next. Thanks

This is open channel tx "c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9" (Sign by electrum broadcast by node)
But I do RBF it replace by tx "3c1e505390269371ac152df474867a15b260a9973c02025c1695bbf2165ad614" (RBF by electrum)

Your environment

• version of lnd 0.16.3
• which operating system (ubuntu)
• version of bitcoin-core, v25.0
• any other relevant environment details

Steps to reproduce

Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.

Expected behaviour

Tell us what should happen

Actual behaviour

Here is log when I use "lncli pendingchannels"

{
"total_limbo_balance": "3996530",
"pending_open_channels": [
],
"pending_closing_channels": [
],
"pending_force_closing_channels": [
],
"waiting_close_channels": [
{
"channel": {
"remote_node_pub": "0294ac3e099def03c12a37e30fe5364b1223fd60069869142ef96580c8439c2e0a",
"channel_point": "c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9:0",
"capacity": "4000000",
"local_balance": "3996530",
"remote_balance": "0",
"local_chan_reserve_sat": "40000",
"remote_chan_reserve_sat": "40000",
"initiator": "INITIATOR_LOCAL",
"commitment_type": "ANCHORS",
"num_forwarding_packages": "0",
"chan_status_flags": "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator",
"private": false
},
"limbo_balance": "3996530",
"commitments": {
"local_txid": "e4832caedc0120f2e7c857f5475672101219ae529bfc75e670794aafe811c62d",
"remote_txid": "61634480014ee03a7ddd8f3f255b9807df7c44000384b84722ac3131742266dd",
"remote_pending_txid": "",
"local_commit_fee_sat": "2810",
"remote_commit_fee_sat": "2810",
"remote_pending_commit_fee_sat": "0"
},
"closing_txid": "e4832caedc0120f2e7c857f5475672101219ae529bfc75e670794aafe811c62d"
}.
]
}

[guggero]

If you RBF a channel funding transaction, you change its TXID, making any pre-signed commitment transaction invalid. So basically you sent your funds to a 2-of-2 multisig address for which you only have one key. So you should NEVER (!!) RBF a channel funding transaction, you MUST use CPFP. The only option you now have to rescue the funds is to use chantools rescuefunding, for which you need your peer's cooperation.

[jiraiyax]

If you RBF a channel funding transaction, you change its TXID, making any pre-signed commitment transaction invalid. So basically you sent your funds to a 2-of-2 multisig address for which you only have one key. So you should NEVER (!!) RBF a channel funding transaction, you MUST use CPFP. The only option you now have to rescue the funds is to use chantools rescuefunding, for which you need your peer's cooperation.

Thank you for your kind. And anyone who know to contact okx lightning team?

[jiraiyax]

If you RBF a channel funding transaction, you change its TXID, making any pre-signed commitment transaction invalid. So basically you sent your funds to a 2-of-2 multisig address for which you only have one key. So you should NEVER (!!) RBF a channel funding transaction, you MUST use CPFP. The only option you now have to rescue the funds is to use chantools rescuefunding, for which you need your peer's cooperation.

Thank you for your kind. And anyone who know to contact okx lightning team?

chantools rescuefunding
--channeldb ~/.lnd/data/graph/mainnet/channel.db
--dbchannelpoint xxxxxxx:xx
--sweepaddr bc1qxxxxxxxxx
--feerate 10

chantools rescuefunding
--confirmedchannelpoint xxxxxxx:xx
--localkeyindex x
--remotepubkey 0xxxxxxxxxxxxxxxx
--sweepaddr bc1qxxxxxxxxx
--feerate 10

is --dbchannelpoint xxxxxxx:xx same with --confirmedchannelpoint xxxxxxx:xx?

[jiraiyax]

I have no luck. after run command the node reply "error fetching UTXO info for outpoint c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9:0: transaction not found"

[ffranr]

Hello @jiraiyax ,

As far as I understand this is the current state of this issue (please correct me if I'm wrong):

• This channel open transaction was broadcast by your node: c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9
• Then you replaced that tx (via RBF) with 3c1e505390269371ac152df474867a15b260a9973c02025c1695bbf2165ad614
• You're attempting to use chantools rescuefunding.

I think --dbchannelpoint should have a different value to --confirmedchannelpoint.

--dbchannelpoint should point to the tx:c2be transaction. And --confirmedchannelpoint should point to the tx:3c1e transaction.

--confirmedchannelpoint string   channel outpoint that got confirmed on chain (<txid>:<txindex>);

error fetching UTXO info for outpoint c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9:0: transaction not found

The error you've reported in your latest message is not unexpected because that tx never made it into the chain.

Please give it a go using --dbchannelpoint and --confirmedchannelpoint, and then let me know how it goes.

[jiraiyax]

Hello @jiraiyax ,

As far as I understand this is the current state of this issue (please correct me if I'm wrong):

• This channel open transaction was broadcast by your node: c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9

• Then you replaced that tx (via RBF) with 3c1e505390269371ac152df474867a15b260a9973c02025c1695bbf2165ad614

• You're attempting to use chantools rescuefunding.

I think --dbchannelpoint should have a different value to --confirmedchannelpoint.

--dbchannelpoint should point to the tx:c2be transaction. And --confirmedchannelpoint should point to the tx:3c1e transaction.

--confirmedchannelpoint string   channel outpoint that got confirmed on chain (<txid>:<txindex>);

error fetching UTXO info for outpoint c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9:0: transaction not found

The error you've reported in your latest message is not unexpected because that tx never made it into the chain.

Please give it a go using --dbchannelpoint and --confirmedchannelpoint, and then let me know how it goes.

Yes, You got it right. How to resolve this solution? Which way I need to do to recovery my money. Thank you.

[jiraiyax]

@ffranr
I got it!
This is base64 encode cHNidP8BAFICAAAAARTWWhbyu5UWXAICPJepYLIVeoZ09C0VrHGTJpBTUB48AAAAAAAAAAAAAdT4PAAAAAAAFgAU76MUxY35k8UoyNVIiHP84C1vi4gAAAAAAAEBKwAJPQAAAAAAIgAg1OXb8O+W/G2QoGvxzCZIrVnnstfV10luzJGHuXWk2BUiAgPDQZRxKpzkc7H6Ga0rXtj6SgFKfS89TNGMyWAeC94CgEgwRQIhAL8sDju7FKPbPRUyXdzsO/u1BOSrwkOYY4YBJiEp7tuaAiBBuMaJd4ETZJMnZnRxUFXGkF+CPy9TvRcGYSfDKwg+CgEBBUdSIQKfb2E0fsHYkhZZv25rkSsi6nLaMdoj42YQD4gd2q+4cyEDw0GUcSqc5HOx+hmtK17Y+koBSn0vPUzRjMlgHgveAoBSrgHMIQKfb2E0fsHYkhZZv25rkSsi6nLaMdoj42YQD4gd2q+4cwAA

Please anyone tell me where I can contact OKX team to do sign transaction for me? Thank you.

[hieblmi]

One way is to contact the okx helpdesk, they offer it on multiple channels https://www.okx.com/community.

[jiraiyax]

If OKX team come and see. Please do signrescuefunding for me. Thank you.

chantools signrescuefunding \ --psbt cHNidP8BAFICAAAAARTWWhbyu5UWXAICPJepYLIVeoZ09C0VrHGTJpBTUB48AAAAAAAAAAAAAdT4PAAAAAAAFgAU76MUxY35k8UoyNVIiHP84C1vi4gAAAAAAAEBKwAJPQAAAAAAIgAg1OXb8O+W/G2QoGvxzCZIrVnnstfV10luzJGHuXWk2BUiAgPDQZRxKpzkc7H6Ga0rXtj6SgFKfS89TNGMyWAeC94CgEgwRQIhAL8sDju7FKPbPRUyXdzsO/u1BOSrwkOYY4YBJiEp7tuaAiBBuMaJd4ETZJMnZnRxUFXGkF+CPy9TvRcGYSfDKwg+CgEBBUdSIQKfb2E0fsHYkhZZv25rkSsi6nLaMdoj42YQD4gd2q+4cyEDw0GUcSqc5HOx+hmtK17Y+koBSn0vPUzRjMlgHgveAoBSrgHMIQKfb2E0fsHYkhZZv25rkSsi6nLaMdoj42YQD4gd2q+4cwAA

[megaptera21]

I have exactly the same problem and also with the OKX node.
Could you ever resolve this @jiraiyax? Do you have a contact with OKX which could help you resolve this?

Thanks!

[jiraiyax]

I have exactly the same problem and also with the OKX node.

Could you ever resolve this @jiraiyax? Do you have a contact with OKX which could help you resolve this?

Thanks!

I've done with my side. Now I try to contact OKX to do they side and I have no idea where to contact with them. I do email to support@okx.com for a while but nothing happen with them side.

[ffranr]

@jiraiyax I'll try to figure out if we have a contact in OKX that I can refer you to. Thanks for keeping this issue updated with your progress.

[jiraiyax]

@jiraiyax I'll try to figure out if we have a contact in OKX that I can refer you to. Thanks for keeping this issue updated with your progress.

Thank you so much for your help.

[megaptera21]

@jiraiyax I'll try to figure out if we have a contact in OKX that I can refer you to. Thanks for keeping this issue updated with your progress.

That would be very useful. I created a ticket with the support e-mail but I don't think this will succeed...

[megaptera21]

@jiraiyax I'll try to figure out if we have a contact in OKX that I can refer you to. Thanks for keeping this issue updated with your progress.

Hi @jiraiyax ! Could you finaly find someone to contact? Would be very helpful, thanks!

[jiraiyax]

@jiraiyax I'll try to figure out if we have a contact in OKX that I can refer you to. Thanks for keeping this issue updated with your progress.

Hi @jiraiyax ! Could you finaly find someone to contact? Would be very helpful, thanks!

No, Sir. Still the same as before.

[megaptera21]

I got a repsone from the OKX Support. Maybe there is some hope...

_Thank you for your patience.

After reviewing your concern, we have escalated the issue for further attention. We kindly request your understanding as we allow sufficient time for the necessary processes to take place. Rest assured, we will ensure that your matter is addressed appropriately and we will provide you with an update once we have received feedback.

Due to the technical complexity of this issue, we regret to inform you that we are unable to provide a specific timeframe for its resolution. However, we assure you that our team is actively working on finding a solution. We sincerely appreciate your patience and understanding in this matter.

Thank you for your understanding and cooperation._

Keep you updated.

[jiraiyax]

I got a repsone from the OKX Support. Maybe there is some hope...

_Thank you for your patience.

After reviewing your concern, we have escalated the issue for further attention. We kindly request your understanding as we allow sufficient time for the necessary processes to take place. Rest assured, we will ensure that your matter is addressed appropriately and we will provide you with an update once we have received feedback.

Due to the technical complexity of this issue, we regret to inform you that we are unable to provide a specific timeframe for its resolution. However, we assure you that our team is actively working on finding a solution. We sincerely appreciate your patience and understanding in this matter.

Thank you for your understanding and cooperation._

Keep you updated.

Thank you so much sir.

[jiraiyax]

Still wait for someone who can help.

[guggero]

Only OKX can help you by counter signing. There is nothing anyone else can do, sorry. Keep trying their helpdesk/support. Closing the issue.