<p>No, it won't.</p>

<p>That's also not possible without rebuilding the UTXO set from scratch, as the unspent outputs being spent need to be known to validate spends against.</p>

<p>If you want to force a revalidation from scratch, start with <code>-reindex-chainstate</code>. This will blow away the UTXO set, and recreate it from the blocks on disk, and revalidate everything in the process (including all signatures, if <code>-assumevalid=0</code> is set).</p>

CC BY-SA 4.0
2019-05-03T04:32:34.780Z
2019-05-03T04:32:34.780Z
Pieter Wuille
<p>I originally synced my node using the Bitcoin Core default <code>assumevalid</code> value. If I set <code>-assumevalid=0</code> in bitcoin.conf and restart my node, will my node go back and validate historical blocks?</p>

<bitcoin-core><bitcoind><signature><transaction-verification><assume-valid>
If I set assumevalid=0 after syncing the blockchain will Bitcoin Core go back and validate historical blocks?
paddy
# If I set assumevalid=0 after syncing the blockchain will Bitcoin Core go back and validate historical blocks?

(Asked by: username_0 on 2019-05-03)

I originally synced my node using the Bitcoin Core default `assumevalid` value. If I set `-assumevalid=0` in bitcoin.conf and restart my node, will my node go back and validate historical blocks?

**Tags:** bitcoin-core, bitcoind, signature, transaction-verification, assume-valid


---

## 1 answers

### Answer by username_1 on 2019-05-03. Score: 9 | Accepted answer

No, it won't.

That's also not possible without rebuilding the UTXO set from scratch, as the unspent outputs being spent need to be known to validate spends against.

If you want to force a revalidation from scratch, start with `-reindex-chainstate`. This will blow away the UTXO set, and recreate it from the blocks on disk, and revalidate everything in the process (including all signatures, if `-assumevalid=0` is set).


---

