<p>Using Bitcoin Core, if you start it with <code>-debug=net</code> (or add <code>debug=net</code> to your bitcoin.conf file), every single network message will be included in the debug.log file along with the node it came from. You can then parse the debug.log file to get the information you want.</p>

CC BY-SA 4.0
2019-05-05T22:39:20.490Z
2019-05-05T22:39:20.490Z
Ava Chow
<p>I am trying to connect to different nodes and keep track of the inventory messages that they send to me. I tried to do this with bitcoinj and libbitcoin, but I didn't make it. The goal is to connect to much nodes as possible and listen to inv messages.</p>

<p>Any help? I am sure there must be a straightforward solution.</p>

<p>Thanks!</p>

<transactions><block>
Tracking inventory messages
Guille
# Tracking inventory messages

(Asked by: username_0 on 2019-05-05)

I am trying to connect to different nodes and keep track of the inventory messages that they send to me. I tried to do this with bitcoinj and libbitcoin, but I didn't make it. The goal is to connect to much nodes as possible and listen to inv messages.

Any help? I am sure there must be a straightforward solution.

Thanks!

**Tags:** transactions, block


---

## 1 answers

### Answer by username_1 on 2019-05-05. Score: 2 | Accepted answer

Using Bitcoin Core, if you start it with `-debug=net` (or add `debug=net` to your bitcoin.conf file), every single network message will be included in the debug.log file along with the node it came from. You can then parse the debug.log file to get the information you want.


---

