HomeBitcoinblockchain fork - Was the "sideloaded" information verified by bitcoind through the...

blockchain fork – Was the “sideloaded” information verified by bitcoind through the worth overflow bug?

As a response to the overflow bug 2010, Satoshi wrote this submit asking individuals to obtain the blockchain (blk****.dat and blkindex.dat) from a selected consumer.

Patch is uploaded to SVN rev 132!

For now, really helpful steps:

  1. Shut down.
  2. Obtain knightmb’s blk
    recordsdata. (substitute your blk0001.dat and blkindex.dat recordsdata)
  3. Improve.
  4. It ought to begin out with lower than 74000 blocks. Let it redownload
    the remaining.

If you happen to do not wish to use knightmb’s recordsdata, you would simply delete your
blk*.dat recordsdata, however it may be quite a lot of load on the community if
everyone seems to be downloading the entire block index without delay.

I am going to construct releases shortly.

I am making an attempt to know from the code whether or not knightmb’s blockchain information could be verified on startup or not, however could not simply decide that.

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



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments