<p>I solved the problem whit CPFP (children pay for parent).</p>

<p>I used the  unconfirmed change of the fund TX stuck in mempool to open a new channel.</p>

<p>At the time of broadcasting TX the median fee is around 150sat/vb, so i chose to slight increase at 200 sat to ensure good probability to push the first fund tx and the second one in the next block avaible.</p>

CC BY-SA 4.0
2020-07-18T11:49:45.197Z
Can you please give me the command using the fund TX stuck in mempool to open a new channel?
When I do a new 'lncli openchannel' I cannot specify the fund TX stuck in mempool. I tried it with the same Public Key and the same local-amt but instead a new channel was opened to this Node. The old unconfirmed transaction still stuck on the mempool. Again: Can you please post how the command TX stuck in mempool to open a new channel looks like? Thanks in advance
MykelSilver2222
CC BY-SA 4.0
2020-05-19T08:50:27.870Z
2020-05-19T08:50:27.870Z
Butta
<p>I got a sweep TX (from a force closed channel) stuck, also due to low fees. This answer is inspired by <a href="https://bitcoin.stackexchange.com/a/96019/99815">OPs answer</a>.</p>
<p>I got it working with:</p>
<pre><code>lncli openchannel \
--sat_per_byte=${fees per byte for the funding transaction of the new channel} \
--min_confs=0 \
${remote nodes id} \
${local amount}
</code></pre>
<p>The <code>--min_confs=0</code> part is the important bit, it allows lnd to use unconfirmed TXes for the funding, but that doesn't mean it will use that particular unconfirmed TX.</p>
<hr />
<p><a href="https://github.com/alexbosworth/balanceofsatoshis" rel="nofollow noreferrer">bos</a> seems to have an option for specifying UTXOs with their <code>bos fund --utxo ${utxo}</code> command. (haven't tested that)</p>
<p><code>bos fund</code> can be used with other commands for example <code>bos open</code> to open (multiple) channels as described <a href="https://www.reddit.com/r/lightningnetwork/comments/m627ms/how_to_batch_open_multiple_channels_at_once_with/gr5bnla/?context=3" rel="nofollow noreferrer">here</a>.</p>

CC BY-SA 4.0
2021-01-23T12:13:57.907Z
2021-09-10T08:04:57.437Z
2021-09-10T08:04:57.437Z
chpio
<p>I have a funding transaction stuck in mempool due to low fees. Searchng around I have find that there is <em>"BumpFee"</em> wallet option to push your transaction. i have tried in this way:</p>

<p><strong>~$ lncli wallet bumpfee [Channel_point] --sat_per_byte 150</strong></p>

<p><strong>>[lncli] rpc error: code = Unknown desc = the passed output doesn't belong to the wallet</strong></p>

<p>When type:</p>

<p><strong>~ $ lncli pendingchannels</strong></p>

<p>i can see the transaction waiting for confirmation, but when type:</p>

<p><strong>~$ lncli wallet pendingsweeps</strong></p>

<blockquote>
  <p>{
                "pending_sweeps": []
    }</p>
</blockquote>

<p>there arent.
The transaction is still present when type:</p>

<p><strong>~ $ lncli listchaintxns</strong></p>

<p>Someone can  try to explain or have had similar behaviour?
Don’t found so much useful stuff in Github</p>

<p><em><a href="https://github.com/lightningnetwork/lnd/blob/master/lnrpc/walletrpc/walletkit.proto" rel="nofollow noreferrer">https://github.com/lightningnetwork/lnd/blob/master/lnrpc/walletrpc/walletkit.proto</a></em></p>

<lightning-network-daemon><ln-opening-channels><child-pays-for-parent><lncli><bumpfee>
LND funding transaction stuck in mempool due to low fees
Butta
# LND funding transaction stuck in mempool due to low fees

(Asked by: username_0 on 2020-05-18)

I have a funding transaction stuck in mempool due to low fees. Searchng around I have find that there is *"BumpFee"* wallet option to push your transaction. i have tried in this way:

**~$ lncli wallet bumpfee [Channel\_point] --sat\_per\_byte 150**

**>[lncli] rpc error: code = Unknown desc = the passed output doesn't belong to the wallet**

When type:

**~ $ lncli pendingchannels**

i can see the transaction waiting for confirmation, but when type:

**~$ lncli wallet pendingsweeps**

> {
> "pending\_sweeps": []
> }

there arent.
The transaction is still present when type:

**~ $ lncli listchaintxns**

Someone can try to explain or have had similar behaviour?
Don’t found so much useful stuff in Github

*<https://github.com/lightningnetwork/lnd/blob/master/lnrpc/walletrpc/walletkit.proto>*

**Tags:** lightning-network-daemon, ln-opening-channels, child-pays-for-parent, lncli, bumpfee


---

## 2 answers

### Answer by username_0 on 2020-05-19. Score: 1

I solved the problem whit CPFP (children pay for parent).

I used the unconfirmed change of the fund TX stuck in mempool to open a new channel.

At the time of broadcasting TX the median fee is around 150sat/vb, so i chose to slight increase at 200 sat to ensure good probability to push the first fund tx and the second one in the next block avaible.

> **Comments:**
> **username_1**: Can you please give me the command using the fund TX stuck in mempool to open a new channel? When I do a new 'lncli openchannel' I cannot specify the fund TX stuck in mempool. I tried it with the same Public Key and the same local-amt but instead a new channel was opened to this Node. The old unconfirmed transaction still stuck on the mempool. Again: Can you please post how the command TX stuck in mempool to open a new channel looks like? Thanks in advance  

---

### Answer by username_2 on 2021-01-23. Score: 1

I got a sweep TX (from a force closed channel) stuck, also due to low fees. This answer is inspired by OPs answer.
I got it working with:
lncli openchannel \
--sat_per_byte=${fees per byte for the funding transaction of the new channel} \
--min_confs=0 \
${remote nodes id} \
${local amount}

The --min_confs=0 part is the important bit, it allows lnd to use unconfirmed TXes for the funding, but that doesn't mean it will use that particular unconfirmed TX.

bos seems to have an option for specifying UTXOs with their bos fund --utxo ${utxo} command. (haven't tested that)
bos fund can be used with other commands for example bos open to open (multiple) channels as described here.


---

