<p>You can check three factors in the <code>getblockchaininfo</code> RPC call:</p>
<p>The result contains a count of the blocks in your chain, and the headers your node has received from peers. For a fully synchronized node, the number of blocks equals the number of headers.</p>
<p>Additionally, there is an <code>initialblockdownload</code> boolean in the response, which will be set to false once the node has caught up with the main chain.</p>

CC BY-SA 4.0
2020-09-24T06:53:44.087Z
is it normal that it's taken several days to syncronize a full node?
kosmosu05
CC BY-SA 4.0
2020-09-24T06:38:04.000Z
2020-09-24T06:38:04.000Z
Raghav Sood
<p>I run a full bitcoin node. I launched it several days ago and it has consumed around 300 GB of traffic already which implies that it is about to finish the initial syncronization process.</p>
<p>Except for that implicit sign, is there a more reliable and concrete way of determinining whether or not a full node has finished the initial syncronization process? Is there a special RPC API call that would return &quot;true&quot; for that?</p>

<bitcoin-core><json-rpc><synchronization><full-node>
How can I know that a full node has finished the initial synchronization process?
kosmosu05
# How can I know that a full node has finished the initial synchronization process?

(Asked by: username_0 on 2020-09-24)

I run a full bitcoin node. I launched it several days ago and it has consumed around 300 GB of traffic already which implies that it is about to finish the initial syncronization process.

Except for that implicit sign, is there a more reliable and concrete way of determinining whether or not a full node has finished the initial syncronization process? Is there a special RPC API call that would return "true" for that?

**Tags:** bitcoin-core, json-rpc, synchronization, full-node


---

## 1 answers

### Answer by username_1 on 2020-09-24. Score: 2 | Accepted answer

You can check three factors in the `getblockchaininfo` RPC call:

The result contains a count of the blocks in your chain, and the headers your node has received from peers. For a fully synchronized node, the number of blocks equals the number of headers.

Additionally, there is an `initialblockdownload` boolean in the response, which will be set to false once the node has caught up with the main chain.

> **Comments:**
> **username_0**: is it normal that it's taken several days to syncronize a full node?  

---

