<p>Bitcoin Core 0.13.0 did not have SegWit's activation parameters (they were added in 0.13.1). This means that after SegWit's activation, your full node was not aware of it, and thus did not ask for or verify block witnesses.</p>

<p>Bitcoin Core is a fully validating node, so after upgrading to 0.15 it noticed that blocks were present that were missing witnesses, and as result also didn't have those witnesses validated. As a result, it is rewinding blocks, undoing the effects of those post-SegWit-no-witness blocks back to SegWit's activation point. When that completes, it will start downloading the blocks again (with witness this time), and validating them.</p>

CC BY-SA 3.0
2017-10-21T06:13:48.490Z
Thanks for the clarification. But what is my fastest way to get it working again?
user2190580
CC BY-SA 3.0
2017-10-21T10:39:39.737Z
Wait until it is done.
Pieter Wuille
CC BY-SA 3.0
2017-10-21T11:58:05.803Z
Increasing dbcache may increase the speed (not just for rewinding, it speeds things up in general), if you have a few hundred MB or GB to spare.
Pieter Wuille
CC BY-SA 4.0
2019-02-22T14:47:43.003Z
Is this advice still current? Currently looking at a 2-3wk process with 7GB ram used and a very normal HDD dedicated to it.
Linef4ult
CC BY-SA 4.0
2019-02-22T14:56:44.767Z
@Linef4ult are you only now upgrading from a version before 0.13.1? If not, this question is not where you should be looking.
Pieter Wuille
CC BY-SA 4.0
2019-02-23T15:38:54.647Z
v11 to v17 upgrade :S
Linef4ult
CC BY-SA 4.0
2019-02-23T16:23:36.857Z
You're very likely better off synchronizing from scratch at this point.
Pieter Wuille
CC BY-SA 4.0
2019-02-23T19:24:55.380Z
While looking at it I'd setup another fresh instance of core on another box. It took about 9hrs or so to catchup. I'll write that over the above upgrader as its still churning. Least the HDD surface got a good refreshing.
Linef4ult
CC BY-SA 3.0
2017-10-20T21:23:41.837Z
2017-10-20T21:23:41.837Z
Pieter Wuille
<p>my blockchain was almost up to date and I wanted do update the Bitcoin core version. The database update was finished in roughly 30 minutes but now I'm stuck on verifying blocks.</p>

<p>Is this normal. How long can this take?</p>

<p>Now it is only repeating following message. But the date is descending?!? I saw other examples where it is ascending.</p>

<pre><code>2017-10-20 15:06:14 Loaded best chain: hashBestChain=00000000000000000083cc7cd6e4643124170b7d69d95b38d17f65a63bb642f3 height=490620 date=2017-10-19 13:56:47 progress=0.998936
2017-10-20 15:06:14 init message: Verifiziere Blöcke...
2017-10-20 15:06:47 UpdateTip: new best=0000000000000000004615a7c3bf2258cb14bdf4b295d3d76e54c6f517779d3a height=490619 version=0x20000000 log2_work=87.310573 tx=263583692 date='2017-10-19 13:53:05' progress=0.998933 cache=1.3MiB(9552txo)
2017-10-20 15:07:26 UpdateTip: new best=00000000000000000041dbf43bd2725fc407bde4df841a9bfbbe3977d394bbb5 height=490618 version=0x20000000 log2_work=87.310534 tx=263581279 date='2017-10-19 13:50:08' progress=0.998930 cache=2.7MiB(19908txo)
2017-10-20 15:08:09 UpdateTip: new best=000000000000000000d16c73923d0ee22ee476f9bab5d4f06b907950b4e604ee height=490617 version=0x20000000 log2_work=87.310495 tx=263579133 date='2017-10-19 13:24:15' progress=0.998912 cache=3.9MiB(30408txo)
2017-10-20 15:08:50 UpdateTip: new best=000000000000000000cdf8fd2ab203fffa8efdce95b150a37171b5d71b479a38 height=490616 version=0x20000000 log2_work=87.310457 tx=263576112 date='2017-10-19 13:18:19' progress=0.998907 cache=5.3MiB(39669txo)
......
2017-10-20 19:29:31 UpdateTip: new best=000000000000000000c8365c1b69b14469257e64063f9fada6a37f5c9f21a9da height=488499 version=0x20000000 log2_work=87.229695 tx=259670084 date='2017-10-06 05:21:41' progress=0.985175 cache=334.7MiB(2186578txo)
2017-10-20 19:29:31 UpdateTip: new best=0000000000000000002c3caefefd142cca83f3edcae575ad663a1017656180df height=488498 version=0x20000000 log2_work=87.229656 tx=259669960 date='2017-10-06 05:21:39' progress=0.985175 cache=334.7MiB(2186636txo)
2017-10-20 19:29:41 UpdateTip: new best=000000000000000000b611b7693a1b26f763c25e8b0b1e66def99bdfa7910ff1 height=488497 version=0x20000000 log2_work=87.229618 tx=259667588 date='2017-10-06 05:08:27' progress=0.985166 cache=335.0MiB(2189168txo)
</code></pre>

<blockchain><bitcoin-core>
Bitcoin Core Update from 0.13 to 0.15 and still verifying block, descending "new best chain"
user2190580
# Bitcoin Core Update from 0.13 to 0.15 and still verifying block, descending "new best chain"

(Asked by: username_0 on 2017-10-20)

my blockchain was almost up to date and I wanted do update the Bitcoin core version. The database update was finished in roughly 30 minutes but now I'm stuck on verifying blocks.

Is this normal. How long can this take?

Now it is only repeating following message. But the date is descending?!? I saw other examples where it is ascending.

```
2017-10-20 15:06:14 Loaded best chain: hashBestChain=00000000000000000083cc7cd6e4643124170b7d69d95b38d17f65a63bb642f3 height=490620 date=2017-10-19 13:56:47 progress=0.998936
2017-10-20 15:06:14 init message: Verifiziere Blöcke...
2017-10-20 15:06:47 UpdateTip: new best=0000000000000000004615a7c3bf2258cb14bdf4b295d3d76e54c6f517779d3a height=490619 version=0x20000000 log2_work=87.310573 tx=263583692 date='2017-10-19 13:53:05' progress=0.998933 cache=1.3MiB(9552txo)
2017-10-20 15:07:26 UpdateTip: new best=00000000000000000041dbf43bd2725fc407bde4df841a9bfbbe3977d394bbb5 height=490618 version=0x20000000 log2_work=87.310534 tx=263581279 date='2017-10-19 13:50:08' progress=0.998930 cache=2.7MiB(19908txo)
2017-10-20 15:08:09 UpdateTip: new best=000000000000000000d16c73923d0ee22ee476f9bab5d4f06b907950b4e604ee height=490617 version=0x20000000 log2_work=87.310495 tx=263579133 date='2017-10-19 13:24:15' progress=0.998912 cache=3.9MiB(30408txo)
2017-10-20 15:08:50 UpdateTip: new best=000000000000000000cdf8fd2ab203fffa8efdce95b150a37171b5d71b479a38 height=490616 version=0x20000000 log2_work=87.310457 tx=263576112 date='2017-10-19 13:18:19' progress=0.998907 cache=5.3MiB(39669txo)
......
2017-10-20 19:29:31 UpdateTip: new best=000000000000000000c8365c1b69b14469257e64063f9fada6a37f5c9f21a9da height=488499 version=0x20000000 log2_work=87.229695 tx=259670084 date='2017-10-06 05:21:41' progress=0.985175 cache=334.7MiB(2186578txo)
2017-10-20 19:29:31 UpdateTip: new best=0000000000000000002c3caefefd142cca83f3edcae575ad663a1017656180df height=488498 version=0x20000000 log2_work=87.229656 tx=259669960 date='2017-10-06 05:21:39' progress=0.985175 cache=334.7MiB(2186636txo)
2017-10-20 19:29:41 UpdateTip: new best=000000000000000000b611b7693a1b26f763c25e8b0b1e66def99bdfa7910ff1 height=488497 version=0x20000000 log2_work=87.229618 tx=259667588 date='2017-10-06 05:08:27' progress=0.985166 cache=335.0MiB(2189168txo)

```

**Tags:** blockchain, bitcoin-core


---

## 1 answers

### Answer by username_1 on 2017-10-20. Score: 2

Bitcoin Core 0.13.0 did not have SegWit's activation parameters (they were added in 0.13.1). This means that after SegWit's activation, your full node was not aware of it, and thus did not ask for or verify block witnesses.

Bitcoin Core is a fully validating node, so after upgrading to 0.15 it noticed that blocks were present that were missing witnesses, and as result also didn't have those witnesses validated. As a result, it is rewinding blocks, undoing the effects of those post-SegWit-no-witness blocks back to SegWit's activation point. When that completes, it will start downloading the blocks again (with witness this time), and validating them.

> **Comments:**
> **username_0**: Thanks for the clarification. But what is my fastest way to get it working again?  
> **username_1**: Wait until it is done.  
> **username_1**: Increasing dbcache may increase the speed (not just for rewinding, it speeds things up in general), if you have a few hundred MB or GB to spare.  
> **username_2**: Is this advice still current? Currently looking at a 2-3wk process with 7GB ram used and a very normal HDD dedicated to it.  
> **username_1**: @username_2 are you only now upgrading from a version before 0.13.1? If not, this question is not where you should be looking.  
> **username_2**: v11 to v17 upgrade :S  
> **username_1**: You're very likely better off synchronizing from scratch at this point.  
> **username_2**: While looking at it I'd setup another fresh instance of core on another box. It took about 9hrs or so to catchup. I'll write that over the above upgrader as its still churning. Least the HDD surface got a good refreshing.  

---

