<p>It means you either have no headers, no block, or both <em>known to be</em> (*) in common with this peer.</p>
<p>From the <code>help</code>:</p>
<pre><code>$ bitcoin-cli help getpeerinfo
....
    &quot;synced_headers&quot; : n,          (numeric) The last header we have in common with this peer
    &quot;synced_blocks&quot; : n,           (numeric) The last block we have in common with this peer
</code></pre>
<p>(*) As Pieter cleared in the comment it doesn't mean you aren't on the same chain, just that the peer didn't announce any block to you yet.</p>

CC BY-SA 4.0
2020-07-23T21:09:41.773Z
Yes I saw that help but are you sure of the meaning of -1? How is that possible that I have no block in common with so many peers, this -1 is not rare I see this all the time.
Strob
CC BY-SA 4.0
2020-07-23T23:18:11.173Z
It's possible because they haven't announced any blocks to you yet. It doesn't mean "no blocks in common", it means "no blocks _known_ to be in common".
Pieter Wuille
CC BY-SA 4.0
2020-07-24T14:20:28.857Z
Ah ok thanks for your reply MR Wuillle. And why they didn't announce any block? What can prevent a node from announcing its blocks?
Strob
CC BY-SA 4.0
2020-07-23T18:28:17.720Z
2020-07-24T11:06:17.000Z
2020-07-24T11:06:17.000Z
Antoine Poinsot
<p>Sometimes I see this in getpeerinfo:</p>
<p>&quot;synced_headers&quot;: -1,
&quot;synced_blocks&quot;: -1,</p>
<p>sometimes it's only synced blocks at -1.</p>
<p>What does that mean?</p>

<bitcoin-core><client><bitcoin-cli><cli><c>
In bitcoin-cli getpeerinf call what does "-1" mean as a "synced_headers" or "synced_blocks" value?
Strob
# In bitcoin-cli getpeerinf call what does "-1" mean as a "synced_headers" or "synced_blocks" value?

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

Sometimes I see this in getpeerinfo:

"synced\_headers": -1,
"synced\_blocks": -1,

sometimes it's only synced blocks at -1.

What does that mean?

**Tags:** bitcoin-core, client, bitcoin-cli, cli, c


---

## 1 answers

### Answer by username_1 on 2020-07-23. Score: 1

It means you either have no headers, no block, or both known to be (*) in common with this peer.
From the help:
$ bitcoin-cli help getpeerinfo
....
    "synced_headers" : n,          (numeric) The last header we have in common with this peer
    "synced_blocks" : n,           (numeric) The last block we have in common with this peer

(*) As Pieter cleared in the comment it doesn't mean you aren't on the same chain, just that the peer didn't announce any block to you yet.

> **Comments:**
> **username_0**: Yes I saw that help but are you sure of the meaning of -1? How is that possible that I have no block in common with so many peers, this -1 is not rare I see this all the time.  
> **username_2**: It's possible because they haven't announced any blocks to you yet. It doesn't mean "no blocks in common", it means "no blocks _known_ to be in common".  
> **username_0**: Ah ok thanks for your reply MR Wuillle. And why they didn't announce any block? What can prevent a node from announcing its blocks?  

---

