Was the "sideloaded" data verified by bitcoind during the value overflow bug?

Question

As a response to the overflow bug 2010, Satoshi wrote this post asking people to download the blockchain (blk****.dat and blkindex.dat) from a specific user.

Patch is uploaded to SVN rev 132!

For now, recommended steps:

1. Shut down.
2. Download knightmb's blk files. (replace your blk0001.dat and blkindex.dat files)
3. Upgrade.
4. It should start out with less than 74000 blocks. Let it redownload the rest.

If you don't want to use knightmb's files, you could just delete your blk*.dat files, but it's going to be a lot of load on the network if everyone is downloading the whole block index at once.

I'll build releases shortly.

I'm trying to understand from the code whether knightmb's blockchain data would be verified on startup or not, but couldn't easily determine that.

Was the blockchain data that people downloaded verified by the code in subversion revision r132 (imported to git commit d4c6b90ca3f9b47adb1b2724a0c3514f80635c84)?

Answer 1

I'm trying to understand from the code whether knightmb's blockchain data would be verified on startup or not, but couldn't easily determine that.

It would not be.

blkindex.dat back then held the equivalent of what is now called the UTXO set (and more). If you'd copy a malicious one, it would be accepted without verification (as it is the outcome of verification itself).