<p>There is a limit of how many messages can be in the ZMQ:</p>

<p><a href="http://api.zeromq.org/2-1:zmq-setsockopt" rel="nofollow noreferrer">http://api.zeromq.org/2-1:zmq-setsockopt</a></p>

<blockquote>
  <p>The ZMQ_HWM option shall set the high water mark for the specified socket. The high water mark is a hard limit on the maximum number of outstanding messages ØMQ shall queue in memory for any single peer that the specified socket is communicating with.</p>
</blockquote>

<p>So you might need to specify the option <code>-zmqpubrawtxhwm</code> to something that is larger than the default of 1000.</p>

CC BY-SA 4.0
2020-01-01T19:00:18.233Z
The question is not about Bitcoin Core. It's about bitcore.io.
0xb10c
CC BY-SA 4.0
2019-08-04T09:54:26.050Z
2019-08-04T09:54:26.050Z
guggero
<p>I'm running a Bitcore.io node and using their ZMQ hook but I've noticed that on livenet not all transactions are actually being sent. I've been comparing it to <a href="https://blockchain.info/unconfirmed-transactions" rel="nofollow noreferrer">https://blockchain.info/unconfirmed-transactions</a> and my realtime logs and can see that some don't appear.</p>

<p>I've also tried creating a transaction to a output address and notifying us of this when it occurs and it hasn't appeared indicating my suspicions are correct.</p>

<p>This only happens on livenet, ran all our tests on testnet and it worked perfectly. Could this have something to do with <code>maxconnections</code>? I've tried increasing it to <code>250</code></p>

<unconfirmed-transactions><bitcore><zeromq>
ZMQ Raw TX doesn't include all transactions
Sladey
# ZMQ Raw TX doesn't include all transactions

(Asked by: username_0 on 2017-05-22)

I'm running a Bitcore.io node and using their ZMQ hook but I've noticed that on livenet not all transactions are actually being sent. I've been comparing it to <https://blockchain.info/unconfirmed-transactions> and my realtime logs and can see that some don't appear.

I've also tried creating a transaction to a output address and notifying us of this when it occurs and it hasn't appeared indicating my suspicions are correct.

This only happens on livenet, ran all our tests on testnet and it worked perfectly. Could this have something to do with `maxconnections`? I've tried increasing it to `250`

**Tags:** unconfirmed-transactions, bitcore, zeromq


---

## 1 answers

### Answer by username_1 on 2019-08-04. Score: 0

There is a limit of how many messages can be in the ZMQ:

<http://api.zeromq.org/2-1:zmq-setsockopt>

> The ZMQ\_HWM option shall set the high water mark for the specified socket. The high water mark is a hard limit on the maximum number of outstanding messages ØMQ shall queue in memory for any single peer that the specified socket is communicating with.

So you might need to specify the option `-zmqpubrawtxhwm` to something that is larger than the default of 1000.

> **Comments:**
> **username_2**: The question is not about Bitcoin Core. It's about bitcore.io.  

---

