hi all. thanks a grest lot for all those ideas. great to feel helped. i then followed all the links provided and again learned quite a lot...and it worked.
using :
lncli wallet bumpclosefee ...( plus the tx id of the opening transaction )
thanks again a lot to you all. great forum
Topic: help needed. strange stuck transaction (Read 130 times)
if you have a look at the transaction it is an LND channel closing transaction. rbf is allowed. pb is the wallet in use is the one from Lnd (not bitcoin core) so some command line related to bitcoincli wallet are not usable.
i don't know how to rbf it... i have important funds there ... can you help ?
RBF isn't going to be simple because the channel's remote node need to co-sign the transaction.i don't know how to rbf it... i have important funds there ... can you help ?
And CPFP in Bitcoin Core should be done manually since there's no specific command to directly create a CPFP transaction.
Good news is it supports "coin control" with send command to do that (CPFP).
Example:
- Find the UTXO created by that unconfirmed transaction with: listunspent 0 command. ("0" is important to include unconfirmed coins)
- Create a PSBT using send command with this format:
bitcoin-cli -rpcwallet=-named send outputs="{\" \": }" inputs="[{\"txid\":\" \",\"vout\": ,\"sequence\":4294967293}]" fee_rate=30
Fill up the inputs field <> with the information from your unconfirmed transaction, you can edit the sequence if you want to disable opt-in rbf flag.
Set the "fee_rate" to your desired value that can bump the child and parent's overall fee rate. (example below) - Depends on the wallet encryption, the above should be enough to broadcast the CPFP transaction and it'll result with "true" together with the txid.
If "false" (wallet is locked); sign the PSBT using walletprocesspsbtcommand. (requires to unlock the wallet to sign either command) - Lastly, broadcast the signed raw transaction with sendrawtransaction
command.
Sample send (Regtest):
Code:
bitcoin-cli --regtest -rpcwallet=descriptor_test -named send outputs="{\"bcrt1qs85jl5ew84q8uk9gz4l4u6glz5cgdn26fm4e4c\": 2.0}" inputs="[{\"txid\":\"e3c7bc999f1f47bb6f0f47a6a41fcbe638c188f5249b7aa1858c535a0f9c2176\",\"vout\":1,\"sequence\":4294967293}]" fee_rate=30Several web font ends for LND such at ride the lightning allow you to do this. Or at least they did, it's been a while since I looked but you could CPFP an onchain TX.
The other option is a paid accelerator. Less work but costs money.
-Dave
if you have a look at the transaction it is an LND channel closing transaction. rbf is allowed. pb is the wallet in use is the one from Lnd (not bitcoin core) so some command line related to bitcoincli wallet are not usable.
i don't know how to rbf it... i have important funds there ... can you help ?
RBF isn't going to be simple because the channel's remote node need to co-sign the transaction.i don't know how to rbf it... i have important funds there ... can you help ?
And CPFP in Bitcoin Core should be done manually since there's no specific command to directly create a CPFP transaction.
Good news is it supports "coin control" with send command to do that (CPFP).
Example:
- Find the UTXO created by that unconfirmed transaction with: listunspent 0 command. ("0" is important to include unconfirmed coins)
- Create a PSBT using send command with this format:
bitcoin-cli -rpcwallet=-named send outputs="{\" \": }" inputs="[{\"txid\":\" \",\"vout\": ,\"sequence\":4294967293}]" fee_rate=30
Fill up the inputs field <> with the information from your unconfirmed transaction, you can edit the sequence if you want to disable opt-in rbf flag.
Set the "fee_rate" to your desired value that can bump the child and parent's overall fee rate. (example below) - Depends on the wallet encryption, the above should be enough to broadcast the CPFP transaction and it'll result with "true" together with the txid.
If "false" (wallet is locked); sign the PSBT using walletprocesspsbtcommand. (requires to unlock the wallet to sign either command) - Lastly, broadcast the signed raw transaction with sendrawtransaction
command.
Sample send (Regtest):
Code:
bitcoin-cli --regtest -rpcwallet=descriptor_test -named send outputs="{\"bcrt1qs85jl5ew84q8uk9gz4l4u6glz5cgdn26fm4e4c\": 2.0}" inputs="[{\"txid\":\"e3c7bc999f1f47bb6f0f47a6a41fcbe638c188f5249b7aa1858c535a0f9c2176\",\"vout\":1,\"sequence\":4294967293}]" fee_rate=30
if you have a look at the transaction it is an LND channel closing transaction. rbf is allowed. pb is the wallet in use is the one from Lnd (not bitcoin core) so some command line related to bitcoincli wallet are not usable.
i don't know how to rbf it... i have important funds there ... can you help ?
thanks
i don't know how to rbf it... i have important funds there ... can you help ?
thanks
If it was LND then the bump fee command from Bitcoin core will not work if that is the command you are trying to use to increase the transaction fee
Did you read the documentation from lightning they have a specific command only for LND why not use those command instead to bump the fee.
Check the two commands for bumping closing fee from this link below
- https://docs.lightning.engineering/lightning-network-tools/lnd/unconfirmed-bitcoin-transactions#docs-internal-guid-5647dd03-7fff-dc71-47cf-5f7e2155a44d
If it doesn't work then you don't have a choice but to use CPFP which was suggested above.
Deciding the ideal fee rate for unilateral exits is indeed a real problem on LN. Mempool was probably empty when you signed a commitment transaction last time with that peer, and it selected very low fee for the potential unilateral exit transaction. I never understood why the software isn't signing several transactions with different fee rates, so that when the user wants to exit, they can choose the fee.
If RBF didn't work, you can try CPFP, but you'll have to pay at least 20 sat/vb, to have the slight priority.
If RBF didn't work, you can try CPFP, but you'll have to pay at least 20 sat/vb, to have the slight priority.
The transaction fee is 1.03 sat/vbyte which is low compared to how mempool is since many months ago. Your node setting is at the fee rate that can not purge the transaction out of mempool at that low fee rate. Increase the fee to 10 sat/vbyte if you want fast confirmation.
hi,
Bitcoin Client Software and Version Number: Bitcoin Core version v26.0.0, LND
Operating System: ubuntu 22
System Hardware Specs: 2Ghtz CPU with 8 GB RAM and 200G free hard drive space.
Description of Problem: stuck LND channel force close transaction .
Any Related Addresses:
Any Related Transaction IDs: a1b517a0f0d822270074a6c18d25f0d42a76eed19bf72b4effcc20354fb95d57
if you have a look at the transaction it is an LND channel closing transaction. rbf is allowed. pb is the wallet in use is the one from Lnd (not bitcoin core) so some command line related to bitcoincli wallet are not usable.
i don't know how to rbf it... i have important funds there ... can you help ?
thanks
Bitcoin Client Software and Version Number: Bitcoin Core version v26.0.0, LND
Operating System: ubuntu 22
System Hardware Specs: 2Ghtz CPU with 8 GB RAM and 200G free hard drive space.
Description of Problem: stuck LND channel force close transaction .
Any Related Addresses:
Any Related Transaction IDs: a1b517a0f0d822270074a6c18d25f0d42a76eed19bf72b4effcc20354fb95d57
if you have a look at the transaction it is an LND channel closing transaction. rbf is allowed. pb is the wallet in use is the one from Lnd (not bitcoin core) so some command line related to bitcoincli wallet are not usable.
i don't know how to rbf it... i have important funds there ... can you help ?
thanks
Jump to: