<p><code>bitcoind -help-debug</code> shows these options, not shown in <code>man bitcoind</code> or <code>bitcoind --help</code>:</p>

<ul>
<li><code>-checkblocks=&lt;n&gt;</code> : Check the last <code>n</code> blocks.  Defaults to <code>6</code>, and <code>0</code> indicates checking all which would take a very long time.</li>
<li><code>-checklevel=&lt;n&gt;</code> : Perform the following verification on each block to be checked, including verifications at lower levels: (defaults to <code>3</code>)

<ul>
<li><code>0</code> : Reads from disk without error</li>
<li><code>1</code> : Blocks are valid</li>
<li><code>2</code> : Blocks have valid undo data</li>
<li><code>3</code> : Look for disconnected tip blocks</li>
<li><code>4</code> : Attempt reconnecting the blocks</li>
</ul></li>
</ul>

<p>Since this is a 5 year old question, at that time, I'm guessing it may have defaulted to more blocks, since you mentioned 288 blocks.</p>

<p>You can lower these values to get it to finish starting and respond faster, but you risk things going horribly wrong if something went wrong the last time it shut down, disk corruption happened, or someone maliciously altered the files.</p>

<p>I'm not sure what caused this, but a while ago, I ran into an error saying "Corruption: block checksum mismatch", so this verification did alert me to there being a problem, allowing me to immediately restore from backups.</p>

CC BY-SA 4.0
2019-09-17T23:43:11.437Z
2019-09-17T23:43:11.437Z
user1902689
<p>It is to verify the block database has not been damaged or tampered with. It does not modify the databases in any way.</p>

CC BY-SA 4.0
2018-11-22T01:55:43.333Z
What does "level 3" mean? Can it be set to a different value to make the verification faster?
rraallvv
CC BY-SA 4.0
2020-05-10T21:33:53.820Z
@rraallvv see other answer
Janus Troelsen
CC BY-SA 3.0
2014-04-17T19:34:10.790Z
2014-04-18T08:11:49.903Z
2014-04-18T08:11:49.903Z
Jori
<p>Upon every start of <code>bitcoind</code>, I see the following in de debug log:</p>

<pre><code>Verifying last 288 blocks at level 3
</code></pre>

<p>come up. At this point, no new blocks have been downloaded and the block chain was 100% up to date when I last closed bitcoin. Bitcoind does not do anything before it has 'verified' these 288 blocks (the server does not answer until this phase has passed).</p>

<ul>
<li>Why do the last blocks need to be verified if nothing new has been added since shutdown?</li>
<li>Does this verification make any changes to any files? Does it save anything to the blocks / chainstate / database directories? </li>
</ul>

<verification>
What is "Verifying last 288 blocks at level 3"?
user
# What is "Verifying last 288 blocks at level 3"?

(Asked by: username_0 on 2014-04-16)

Upon every start of `bitcoind`, I see the following in de debug log:

```
Verifying last 288 blocks at level 3

```

come up. At this point, no new blocks have been downloaded and the block chain was 100% up to date when I last closed bitcoin. Bitcoind does not do anything before it has 'verified' these 288 blocks (the server does not answer until this phase has passed).

* Why do the last blocks need to be verified if nothing new has been added since shutdown?
* Does this verification make any changes to any files? Does it save anything to the blocks / chainstate / database directories?

**Tags:** verification


---

## 2 answers

### Answer by username_1 on 2019-09-17. Score: 4

`bitcoind -help-debug` shows these options, not shown in `man bitcoind` or `bitcoind --help`:

* `-checkblocks=<n>` : Check the last `n` blocks. Defaults to `6`, and `0` indicates checking all which would take a very long time.
* `-checklevel=<n>` : Perform the following verification on each block to be checked, including verifications at lower levels: (defaults to `3`)
  + `0` : Reads from disk without error
  + `1` : Blocks are valid
  + `2` : Blocks have valid undo data
  + `3` : Look for disconnected tip blocks
  + `4` : Attempt reconnecting the blocks

Since this is a 5 year old question, at that time, I'm guessing it may have defaulted to more blocks, since you mentioned 288 blocks.

You can lower these values to get it to finish starting and respond faster, but you risk things going horribly wrong if something went wrong the last time it shut down, disk corruption happened, or someone maliciously altered the files.

I'm not sure what caused this, but a while ago, I ran into an error saying "Corruption: block checksum mismatch", so this verification did alert me to there being a problem, allowing me to immediately restore from backups.


---

### Answer by username_2 on 2014-04-17. Score: 2

It is to verify the block database has not been damaged or tampered with. It does not modify the databases in any way.

> **Comments:**
> **username_3**: What does "level 3" mean? Can it be set to a different value to make the verification faster?  
> **username_4**: @username_3 see other answer  

---

