<p>As of <strong>0.14.0</strong>, when you receive a <code>verack</code>, you also need to send a <code>verack</code> message back.</p>

<p>So whereas before you could do this:</p>

<pre><code>Client: version
Node:   version
Node:   verack
......
</code></pre>

<p>You now need to do this:</p>

<pre><code>Client: version
Node:   version
Node:   verack
Client: verack  &lt;- do this!
......
</code></pre>

<hr>

<p><strong>Links</strong></p>

<ul>
<li><a href="https://bitcoin.org/en/release/v0.14.0" rel="nofollow noreferrer">https://bitcoin.org/en/release/v0.14.0</a> (#9715)</li>
<li><a href="https://github.com/bitcoin/bitcoin/pull/9715" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/pull/9715</a></li>
</ul>

CC BY-SA 3.0
2017-05-13T13:21:14.420Z
2017-05-13T13:34:50.933Z
2017-05-13T13:34:50.933Z
inersha
<p>I've written my own simple client that connects to my local node. It has been working fine, but after upgrading from <strong>13.1</strong> to <strong>14.1</strong> my local node is no longer sending my client <code>inv</code> messages.</p>

<p>The handshake seems to be working fine, as follows:</p>

<pre><code>Client: version
Node:   version
Node:   verack
......
</code></pre>

<p>But after the <code>verack</code>, the node does not send any more data to me. I usually get a <code>ping</code> after the <code>verack</code>, but that's not coming through either.</p>

<p>Any ideas why this might be happening? Here's the payload of the verack I'm receiving, if it's any use:</p>

<pre><code>37663131303130303064303030303030303030303030303035613034313735393030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303064303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303034626363303539623666653837346333323132663533363137343666373336383639336133303265333133343265333132383463363536313732366534643635343134323639373436333666363936653239326631363164303730303031
</code></pre>

CC BY-SA 3.0
2017-05-13T15:01:24.193Z
+2 Thanks for sharing your discovery with us!
Murch
<network>
No longer receiving inv messages from node
inersha
# No longer receiving inv messages from node

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

I've written my own simple client that connects to my local node. It has been working fine, but after upgrading from 13.1 to 14.1 my local node is no longer sending my client inv messages.
The handshake seems to be working fine, as follows:
Client: version
Node:   version
Node:   verack
......

But after the verack, the node does not send any more data to me. I usually get a ping after the verack, but that's not coming through either.
Any ideas why this might be happening? Here's the payload of the verack I'm receiving, if it's any use:
37663131303130303064303030303030303030303030303035613034313735393030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303064303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303034626363303539623666653837346333323132663533363137343666373336383639336133303265333133343265333132383463363536313732366534643635343134323639373436333666363936653239326631363164303730303031

**Tags:** network

> **Comments:**
> **username_1**: +2 Thanks for sharing your discovery with us!  

---

## 1 answers

### Answer by username_0 on 2017-05-13. Score: 2 | Accepted answer

As of 0.14.0, when you receive a verack, you also need to send a verack message back.
So whereas before you could do this:
Client: version
Node:   version
Node:   verack
......

You now need to do this:
Client: version
Node:   version
Node:   verack
Client: verack  <- do this!
......


Links

https://bitcoin.org/en/release/v0.14.0 (#9715)
https://github.com/bitcoin/bitcoin/pull/9715


---

