<p>I created a bitcoin transaction from <code>lnd</code> (<code>lncli sendcoins</code>), and it seems to be created successfully and I can see it in my local <code>bitcoind</code> mempool:</p>
<pre><code>bitcoin-cli getmempoolentry abdctxid {
 &quot;vsize&quot;: 130,
 &quot;weight&quot;: 520,
 &quot;time&quot;: 1692559301,
 &quot;height&quot;: 804102,
 &quot;descendantcount&quot;: 1,
 &quot;descendantsize&quot;: 130,
 &quot;ancestorcount&quot;: 1,
 &quot;ancestorsize&quot;: 130,
 &quot;wtxid&quot;: &quot;bcdetxid&quot;,
 &quot;fees&quot;: {
   &quot;base&quot;: 0.00000786,
   &quot;modified&quot;: 0.00000786,
   &quot;ancestor&quot;: 0.00000786,
   &quot;descendant&quot;: 0.00000786
 },
 &quot;depends&quot;: [
 ],
 &quot;spentby&quot;: [
 ],
 &quot;bip125-replaceable&quot;: false,
 &quot;unbroadcast&quot;: false
}
</code></pre>
<p>It is however not being broadcasted further, the receiver did not see the transaction, and it is not visible in various online explorers.</p>
<p>Using Bitcoin Core v23.0.0. The only non-default setting in my config is <code>minrelaytxfee=0.00000011 blockmintxfee=0.00000011 maxmempool=300</code>.</p>
<p>As far as I know this is the first time in years it happened to my node. What could be the reason for the transaction being stuck in my local mempool and is there a way to force-rebroadcast it further?</p>

CC BY-SA 4.0
2023-08-24T08:30:58.210Z
It's hard to tell with so little information. Anything else uncommon? Do you have peers at all (`getpeerinfo`)? Any high CPU usage from the `bitcoind` process? Anything peculiar in the `debug.log`? Have you tried upgrading you `bitcoind` to the latest (25.0) version or at least the patched (23.2) version?
Antoine Poinsot
CC BY-SA 4.0
2023-08-24T11:51:07.160Z
Thanks for directions! `getpeerinfo` shows ~50 peers, no suspiciously high CPU usage, upgrading to `23.2` does not help. Grepping `debug.log` for the txid or "mempool" or "err" does not show anything interesting. Really not sure what else to check...
Dmitry Laptev
CC BY-SA 4.0
2023-08-24T12:03:57.000Z
Out of all the things, restarting `lnd` helped! Maybe there is some logic on the wallet side that forced transaction to be rebroadcasted, but now it is visible to other nodes as well. Still super weird that this happened though.
Dmitry Laptev
<bitcoin-core><bitcoind><mempool><lightning-network-daemon>
Transaction in local mempool not broadcasted further
Dmitry Laptev
# Transaction in local mempool not broadcasted further

(Asked by: username_0 on 2023-08-24)

I created a bitcoin transaction from `lnd` (`lncli sendcoins`), and it seems to be created successfully and I can see it in my local `bitcoind` mempool:

```
bitcoin-cli getmempoolentry abdctxid {
 "vsize": 130,
 "weight": 520,
 "time": 1692559301,
 "height": 804102,
 "descendantcount": 1,
 "descendantsize": 130,
 "ancestorcount": 1,
 "ancestorsize": 130,
 "wtxid": "bcdetxid",
 "fees": {
   "base": 0.00000786,
   "modified": 0.00000786,
   "ancestor": 0.00000786,
   "descendant": 0.00000786
 },
 "depends": [
 ],
 "spentby": [
 ],
 "bip125-replaceable": false,
 "unbroadcast": false
}

```

It is however not being broadcasted further, the receiver did not see the transaction, and it is not visible in various online explorers.

Using Bitcoin Core v23.0.0. The only non-default setting in my config is `minrelaytxfee=0.00000011 blockmintxfee=0.00000011 maxmempool=300`.

As far as I know this is the first time in years it happened to my node. What could be the reason for the transaction being stuck in my local mempool and is there a way to force-rebroadcast it further?

**Tags:** bitcoin-core, bitcoind, mempool, lightning-network-daemon

> **Comments:**
> **username_1**: It's hard to tell with so little information. Anything else uncommon? Do you have peers at all (`getpeerinfo`)? Any high CPU usage from the `bitcoind` process? Anything peculiar in the `debug.log`? Have you tried upgrading you `bitcoind` to the latest (25.0) version or at least the patched (23.2) version?  
> **username_0**: Thanks for directions! `getpeerinfo` shows ~50 peers, no suspiciously high CPU usage, upgrading to `23.2` does not help. Grepping `debug.log` for the txid or "mempool" or "err" does not show anything interesting. Really not sure what else to check...  
> **username_0**: Out of all the things, restarting `lnd` helped! Maybe there is some logic on the wallet side that forced transaction to be rebroadcasted, but now it is visible to other nodes as well. Still super weird that this happened though.  

---

## 0 answers

