<p>It appears that <code>btcwire</code> is the Bitcoin p2p module of <code>btcd</code> and <code>neutrino</code> is Lightning Labs's implementation of BIP157/158 (compact client-side block filters (CBF)). I suspect that the agent identifier <code>btcwire 0.5.0/neutrino</code> indicates LND (Lightning Network Daemon) instances which are configured to allow or prefer CBF for synchronization. Given your experience and since CBF support was only added to Bitcoin Core in 0.21.0, it looks like the demand for the CBF network service far outstrips the few listening nodes that provide the CBF network service at this time.</p>
<p>I expect that the load will be distributed better as more Bitcoin Core 0.21.0 listening nodes come online.</p>

CC BY-SA 4.0
2021-02-05T16:26:50.213Z
2021-02-05T16:26:50.213Z
Murch
<p>I run Bitcoin Core 0.21.0 from a data center, unmetered, with compact block filters enabled (<code>blockfilterindex=1</code> <code>peerblockfilters=1</code>).</p>
<p>Soon after the restart, I get a huge number (140-200) of connections identifying as <code>btcwire 0.5.0/neutrino</code>, from all over the world. They are responsible for vast majority of download bandwidth (90%+).</p>
<p>This only happens when node is signalling CBF support via <code>peerblockfilters=1</code>.</p>
<p>I am aware &quot;Neutrino&quot; is a proof-of-concept light wallet using CBF but it doesn't explain neither the vast dominance in terms of connections number (~75%), nor in terms of bandwidth (90%+).</p>
<p>Incidentally, &quot;Neutrino&quot; is also a surveillance company owned by Coinbase :)</p>
<p>Any guidance is welcome!</p>

<bitcoin-core><bitcoind><network><connection><compact-client-side-block-filters>
With peerblockfilters=1 hundreds of "btcwire 0.5.0/neutrino" connections are downloading TB from my Bitcoin node
qertoip
# With peerblockfilters=1 hundreds of "btcwire 0.5.0/neutrino" connections are downloading TB from my Bitcoin node

(Asked by: username_0 on 2021-02-05)

I run Bitcoin Core 0.21.0 from a data center, unmetered, with compact block filters enabled (`blockfilterindex=1` `peerblockfilters=1`).

Soon after the restart, I get a huge number (140-200) of connections identifying as `btcwire 0.5.0/neutrino`, from all over the world. They are responsible for vast majority of download bandwidth (90%+).

This only happens when node is signalling CBF support via `peerblockfilters=1`.

I am aware "Neutrino" is a proof-of-concept light wallet using CBF but it doesn't explain neither the vast dominance in terms of connections number (~75%), nor in terms of bandwidth (90%+).

Incidentally, "Neutrino" is also a surveillance company owned by Coinbase :)

Any guidance is welcome!

**Tags:** bitcoin-core, bitcoind, network, connection, compact-client-side-block-filters


---

## 1 answers

### Answer by username_1 on 2021-02-05. Score: 7

It appears that `btcwire` is the Bitcoin p2p module of `btcd` and `neutrino` is Lightning Labs's implementation of BIP157/158 (compact client-side block filters (CBF)). I suspect that the agent identifier `btcwire 0.5.0/neutrino` indicates LND (Lightning Network Daemon) instances which are configured to allow or prefer CBF for synchronization. Given your experience and since CBF support was only added to Bitcoin Core in 0.21.0, it looks like the demand for the CBF network service far outstrips the few listening nodes that provide the CBF network service at this time.

I expect that the load will be distributed better as more Bitcoin Core 0.21.0 listening nodes come online.


---

