<p>It looks like the magic bytes you are using isn't the Bitcoin magic bytes. You have <code>e3e1f3e8</code> but Bitcoin's network magic is <code>f9beb4d9</code>.</p>

CC BY-SA 4.0
2020-07-17T20:46:47.863Z
Sorry i should have clarified, i'm trying to connect to a BSV node
Michael Fletcher
CC BY-SA 4.0
2020-07-17T18:48:18.777Z
2020-07-17T18:48:18.777Z
Ava Chow
<p>It seems my 'getheaders' request is being ignored by peers. I've followed the implementation: <a href="https://en.bitcoin.it/wiki/Protocol_documentation#getheaders" rel="nofollow noreferrer">https://en.bitcoin.it/wiki/Protocol_documentation#getheaders</a> without success.</p>
<p>If I change it to 'getblocks' then it returns an inv[500] message just fine. But for some reason, it's not returning a 'headers' packet when requesting headers.</p>
<p>I'm connected to over 100 peers, and still no success.</p>
<p>Has anyone else had similar trouble before? Any guidance is appreciated.</p>
<p>The request values are as follows:</p>
<pre><code>    magic=3908297187
    command=getheaders
    length=69 
    checksum=1021834552
    payload=[version=70013, hashCount=1, blockLocatorHash=[00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048], hashStop=0000000000000000000000000000000000000000000000000000000000000000]
</code></pre>
<p>and the encoded bytes are:</p>
<pre><code>e3e1f3e876657273696f6e000000000069000000a4d49d4e7d11010004000000000000002cb0db5d73010000000000000000000000000000000000000000ffff7f000001208d000000000000000000000000000000000000ffff0fa518f420a100ecfbdaa2585542132f626974636f696e6a2d73763a302e302e372f0000000000
</code></pre>
<p><em>Just to note, when serializing, i reverse the blockLocatorHash bytes as mentioned in the wiki.</em></p>
<p>Cheers,</p>

CC BY-SA 4.0
2020-07-17T17:12:14.760Z
It would likely help answerers if you were to share the actual request that you are sending, and the response that you are receiving.
Murch
CC BY-SA 4.0
2020-07-17T17:49:45.077Z
Thanks for the response. I've updated my question.
Michael Fletcher
CC BY-SA 4.0
2020-07-17T18:08:11.733Z
Do you get any messages in debug.log on the node you're querying, if you enable `-debug=net`?
Pieter Wuille
CC BY-SA 4.0
2020-07-17T18:17:23.013Z
I'm pushing the raw transaction to remote peers without response, and there's nothing to suggest the message didn't send unsuccessfully.
Michael Fletcher
CC BY-SA 4.0
2020-07-17T21:43:47.773Z
Voting to close as the asker clarified that they are troubleshooting communication with some altcoin client.
Murch
<client><network><protocol><bitcoinj><bitcoin-sv>
getheaders request being ignored by peers
Michael Fletcher
# getheaders request being ignored by peers

(Asked by: username_0 on 2020-07-17)

It seems my 'getheaders' request is being ignored by peers. I've followed the implementation: <https://en.bitcoin.it/wiki/Protocol_documentation#getheaders> without success.

If I change it to 'getblocks' then it returns an inv[500] message just fine. But for some reason, it's not returning a 'headers' packet when requesting headers.

I'm connected to over 100 peers, and still no success.

Has anyone else had similar trouble before? Any guidance is appreciated.

The request values are as follows:

```
    magic=3908297187
    command=getheaders
    length=69 
    checksum=1021834552
    payload=[version=70013, hashCount=1, blockLocatorHash=[00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048], hashStop=0000000000000000000000000000000000000000000000000000000000000000]

```

and the encoded bytes are:

```
e3e1f3e876657273696f6e000000000069000000a4d49d4e7d11010004000000000000002cb0db5d73010000000000000000000000000000000000000000ffff7f000001208d000000000000000000000000000000000000ffff0fa518f420a100ecfbdaa2585542132f626974636f696e6a2d73763a302e302e372f0000000000

```

*Just to note, when serializing, i reverse the blockLocatorHash bytes as mentioned in the wiki.*

Cheers,

**Tags:** client, network, protocol, bitcoinj, bitcoin-sv

> **Comments:**
> **username_1**: It would likely help answerers if you were to share the actual request that you are sending, and the response that you are receiving.  
> **username_0**: Thanks for the response. I've updated my question.  
> **username_2**: Do you get any messages in debug.log on the node you're querying, if you enable `-debug=net`?  
> **username_0**: I'm pushing the raw transaction to remote peers without response, and there's nothing to suggest the message didn't send unsuccessfully.  
> **username_1**: Voting to close as the asker clarified that they are troubleshooting communication with some altcoin client.  

---

## 1 answers

### Answer by username_3 on 2020-07-17. Score: 2

It looks like the magic bytes you are using isn't the Bitcoin magic bytes. You have `e3e1f3e8` but Bitcoin's network magic is `f9beb4d9`.

> **Comments:**
> **username_0**: Sorry i should have clarified, i'm trying to connect to a BSV node  

---

