0

Sometimes I see this in getpeerinfo:

"synced_headers": -1, "synced_blocks": -1,

sometimes it's only synced blocks at -1.

What does that mean?

Strob
  • 21
  • 3

1 Answers1

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.

Antoine Poinsot
  • 5,881
  • 2
  • 11
  • 28
  • 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 Jul 23 '20 at 21:09
  • 1
    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 Jul 23 '20 at 23:18
  • 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 Jul 24 '20 at 14:20