[ANN] Bitcoin blockchain data torrent

Quote from: deepceleron on January 08, 2014, 09:22:19 PM

Quote from: Sukrim on January 08, 2014, 09:11:27 PM

IF there is actual bitcoin data in there, yes. Unless jgarzik finally gets around to extending the python script to deterministically also create torrent infohashes from blockchain data, I'd rather take no chances though.

Please publish the SHA256 & MD5 of the final bootstrap.dat file that you created to 279000. I will be able to tell you if it can be independently created by others with identical data. I can recreate jgarzik's from network-downloaded blocks.

Blockchain data is fully signature-checked for all blocks since the last code checkpoint. This means that CPU, and not network bandwidth, is usually the limiting factor processing blocks 250,000 and on. It is not really beneficial to download more data before getting the Bitcoin CPU work started, which is why the torrent corresponds with the checkpoint.

i made my with bitcoin / contrib / linearize from bitcoin gitrepo

here the sum's:

md5: 8013a545e8d262a462fc33c5dd88951c bootstrap.dat

SHA256: 1de3dc1a035aa82db6b75029de80a8d4fb8d4fe07ad16f085a9d30186b018b52 bootstrap.dat

Quote from: Subo1977 on January 08, 2014, 09:38:03 PM

Quote from: deepceleron on January 08, 2014, 09:22:19 PM

Quote from: Sukrim on January 08, 2014, 09:11:27 PM

update:

magnet:?xt=urn:btih:F01BD4AD9255447678C1C90D4FADF1BE0E8F53A4&dn=bootstrap.dat&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.ccc.de%3a80%2fannounce

bootstrap.dat.torrent download:
https://mega.co.nz/#!bQMR1YKQ!eix60XZmevco2kim6czKTxiPJrNBSQpNMILJRc1lpuw

Updated the torrent to block 279,000. See top post. Please start seeding the new one!

For existing seeders, just swap out your .torrent file with the new one, and you will resume at ~70% completion.

http://sourceforge.net/projects/bitcoin/files/Bitcoin/blockchain/bootstrap.dat.torrent/download

Quote from: jgarzik on January 11, 2014, 07:11:31 PM

Great work. THX.

Switched my Seedboxes.

The 250K bootstrap.dat saved me lots of time while I effed around with my server not realizing I was dealing with a bad hard drive. I was deleting all block data and reloading it from bootstrap.dat probably twice a day. I've overridden my global upload limit on the updated torrent so that I can help support this even better. Thank you.

Seeding with my 500 Mbps box. Cool

Add a 500 Mbps box in NL to my 1000mbps box in FR.

lets Rock

I will be another seed in 2 hours

Suggestions for better trackers are always welcome. Trackers appear and disappear, and I'm certainly not an expert on picking them.

Ideally we would use trackerless torrents (pure DHT), but that early experiment ended in failure.

or setup an own tracker at ee bitcoin.org or so...

I just imported the key at http://bitcoin.org/jgarzik-bitpay.asc and then ran:

'$ gpg --verify'

... on the January 11, 2014 pgp signed text contained in the the first post of this thread. It just gave me the output:

gpg: Signature made Sat 11 Jan 2014 19:04:44 GMT using RSA key ID A2DB9CCA
gpg: BAD signature from "Jeff Garzik <jgarzik@bitpay.com>"

Is anybody else getting this problem?

Quote from: jonathan on January 14, 2014, 05:10:04 AM

I just imported the key at the http://bitcoin.org/jgarzik-bitpay.asc and then ran:

'$ gpg --verify'

... on the January 11, 2014 pgp signed text contained in the the first post of this thread. It just gave me the output:

gpg: Signature made Sat 11 Jan 2014 19:04:44 GMT using RSA key ID A2DB9CCA
gpg: BAD signature from "Jeff Garzik <jgarzik@bitpay.com>"

Is anybody else getting this problem?

Same here

Quote from: Subo1977 on January 14, 2014, 08:50:13 AM

Quote from: jonathan on January 14, 2014, 05:10:04 AM

gpg: BAD signature from "Jeff Garzik <jgarzik@bitpay.com>"
Is anybody else getting this problem?

Same here

Does it mean the signature is forged?

It may mean the message we are getting at the browser is not the message Jeff signed.

If this is the case, then there often winds up being an innocent explanation for it, such as that forum software is introducing unwanted line-breaks into the message, or something like that. But at worst, it may mean someone has altered the message.

Maybe it would be better if jgarzik would wrap the statement in [ code ] tags

Code:

like this

as it preserves whitespace?

Updated OP to use a code block, and also posted the original GPG-signed msg at http://gtf.org/garzik/bitcoin/torrent-msg.txt

Let me know if sigs still fail.

Hi Jeff,

This one gives a good sig: http://gtf.org/garzik/bitcoin/torrent-msg.txt

... but the code block in this thread's OP is still bad. Diff check shows a line break at line four in the good message (ie., the file at gtf.org), whereas line four in this thread's OP code block goes straight to the text.

Thanks for attending to this Jeff.

24 hours / 90 GB uploadet with my seedbox :-)

I add a new Torrent to my seeders:

A Bootstrap.dat containing the Blocks from 279000 to 282000 ( 460 MB).

Here the Magnet:
magnet:?xt=urn:btih:6BDE914DB48DA35A2F9AFD5B08B4DC1DFF7DBA5B&dn=bootstrap_279000_up.dat&tr=http%3a%2f%2ftracker.ex.ua%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=http%3a%2f%2fcoppersurfer.tk%3a6969%2fannounce&tr=http%3a%2f%2ftracker.ex.ua%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=http%3a%2f%2fi.bandito.org%2fannounce&tr=http%3a%2f%2ftracker.marshyonline.net%2fannounce&tr=http%3a%2f%2fexodus.desync.com%2fannounce&tr=udp%3a%2f%2ftracker.ex.ua%3a80%2fannounce&tr=http%3a%2f%2ftracker.tfile.me%2fannounce

and here is the .torrent

https://github.com/Subo1978/Bootstrap.dat

Have fun

Quote from: Subo1977 on January 23, 2014, 02:56:49 PM

Quick question: if we have already synced up to 279k blocks with our qt wallet, can we use your bootstrap_279000_up.dat file by itself
to update the remaining blocks?

Or do we also need the entire bootstrap.dat additionally with previous blocks?

Thanks for your help!
Stewart

EDIT: This does work with the partial bootstrap file. I just had to make sure to re-start the wallet after adding the bootstrap file.
Normally, I would be waiting for hours get these last 4k blocks synched in the wallet, now its just taking a few minutes.
Thanks for the bootstrap file!!!