No surprises comparing this file (sha256sum d05062052be4dd6fbaeac5f17598e52f7ad545f9f938acefaf7067ecce1d7b5a) with the blockchain.  I hope posting these verifications is useful to others.

I'm doing it this way because it's faster to stream data out of bootstrap.dat rather than pulling the data out of bitcoin-cli.  So I can generate the sha256sum from the client once for a given range, and use it to verify that the data hasn't changed.  Future updates just need a checksum out of bitcoin-cli covering the new parts.  If anyone's interested in the blockheight program, I can publish it.

Blocks 0 through 295000, bootstrap matches blockchain:


Blocks 295001 through 313000, bootstrap matches blockchain:


Blocks 313001 through 317000, bootstrap matches blockchain:

See post on page 12:

Since I was curious about the new torrent, here's some info:

new bootstrap.dat contains up to block height 313000 (July 8 )

The new block data (this is using the hexidecimal form) matches my bitcoind's:

$ ./blockheight -l 295001 < bootstrap-313000.dat | sha256sum
6cccd54b215799d91b6781b190903fb5673cf6413d2a93c5ebe26223e3b2de21  -
$ for((i = 295001; i < 313001; i++)); do  ./bitcoin-cli getblock `./bitcoin-cli getblockhash $i` false ; done | sha256sum
6cccd54b215799d91b6781b190903fb5673cf6413d2a93c5ebe26223e3b2de21  -

Previous data matches:

$ dd if=bootstrap-313000.dat bs=335633 count=52206 2>/dev/null | sha1sum
78a4b41ba7ed823c78cd9ca81a6de393c0ccc226  -
$ sha1sum bootstrap-295000.dat
78a4b41ba7ed823c78cd9ca81a6de393c0ccc226  bootstrap-295000.dat


Can you re-add a http:// based tracker?  The UDP trackers aren't supported by older transmission (2.13 from EPEL).  The exodus.desync.com tracker in the previous torrent seems to be working well.

Edit: UDP trackers actually do support IPv6, but support varies depending on your torrent software.