How to re-verify blockchain using imported data

[ragnar dannesk gold]

I wanted to see how long my machine would take to re-verify the Bitcoin blockchain, but without having bandwidth limitations (so I still want to use the blockchain I have downloaded).

Is there a way to get Bitcoin core to use this data, but to not trust it? And re-verify from block 1?

I'm guessing I'd have to delete a file (possibly 'chainstate' folder?) and start Core again.

Any help is much appreciated!

[1714060013]

1714060013

[1714060013]

1714060013

[ragnar dannesk gold]

I see it will be:

-reindex-chainstate   Rebuild chain state from the currently indexed blocks
-reindex   Rebuild chain state and block index from the blk*.dat files on disk


I'm guessing reindex? Although I'm not sure of the difference. Anyone?

[ragnar dannesk gold]

-reindex:


-reindex

Method not found (code -32601)

And

-verifychain  checks something but only takes 5 seconds to do.

[JeromeTash]

So sad no one is able to instantly help you from this board. Could you please try moving the topic to Bitcoin Technical Support?
You could easily get someone there with much more experience to help you out.
The move topic button is on the bottom left of your page. I hope you get helped out ASAP.

[ragnar dannesk gold]

Thanks Jerome. I figured it out.

In case anyone else has this question, my problem was because I was using '-reindex' in the console, rather than adding it to the bitcoin-qt.exe to run (via command line- "Z:\Bitcoin\bitcoin-qt -reindex").

I am not sure whether deleting chainstate would have cause issues, but it does seem that reindex has done that and synced from block 1 to (currently) August 2018 in 3 hours using only 13MB of bandwidth. HDD bottlenecked for the first 8 years, and CPU for the last 2 years worth.

Edit - Finished reindex in ~4 Hours on a 5 year old PC (7200rpm HDD, i5 4690 CPU, 16gb RAM (dbcache set to 12,000)).

[KingZee]

Thanks Jerome. I figured it out.

In case anyone else has this question, my problem was because I was using '-reindex' in the console, rather than adding it to the bitcoin-qt.exe to run (via command line- "Z:\Bitcoin\bitcoin-qt -reindex").

I am not sure whether deleting chainstate would have cause issues, but it does seem that reindex has done that and synced from block 1 to (currently) August 2018 in 3 hours using only 13MB of bandwidth. HDD bottlenecked for the first 8 years, and CPU for the last 2 years worth.

Its nice you figured that on your own I was about to write a post telling you it's a runtime parameter, but here's a merit. Good luck running your node!