Pages:
Author

Topic: **Download the blockchain here, updated regularly ** - page 4. (Read 97741 times)

sr. member
Activity: 443
Merit: 251
Bitcoin Blockchain Download [bootstrap.dat]

About
Code:
block date:     Sa. 29 Jul. 2017 09:31:58
block number:   #478100
file name:      bootstrap.dat.xz
file size:      ~82 GB [83,729 MB]
file format:    compressed xz (containing bootstrap.dat)
uncompressed:   ~119 GB

Indexed with Bitcoin Core v0.14.2 on Linux (4.4.0 x64) platform.

What's new
The compression format has been updated to xz which allows the decompression of the bootstrap.dat file while downloading it. If you are an expert you can use system pipes to inject the highly compressed serialized Bitcoin blockchain bootstrap.dat to the Bitcoin Core initial blockchain loadup process.

Setup
Move the decompressed bootstrap.dat into your Bitcoin-Qt application folder and (re)start your Bitcoin-Qt client:
  • Unix/Linux: ~/.bitcoin
  • MAC OS X: ~/Library/Application Support/Bitcoin/
  • Windows: [User Directory]AppDataRoamingBitcoin (i.e. C:UsersMyUsernameAppDataRoamingBitcoin

If you don't know how it works you can check the details on the download page.
Beware that after decompressing the XY file, you need additional ~140 GB to import the bootstrap file!


Download
--- https://goo.gl/gdHA8S ---

Hint
This is a private hosted download. To scope the hosting costs the download page requires a donation of whatever amount is suitable for you.
sr. member
Activity: 443
Merit: 251
Bitcoin Blockchain Download [bootstrap.dat]

About
Code:
block date:     Tu. 18 Jul. 2017 16:13:56
block number:   #476400
file name:      bootstrap.dat.xz
file size:      ~80 GB [82,644 MB]
file format:    compressed xz (containing bootstrap.dat)
uncompressed:   ~116 GB

Indexed with Bitcoin Core v0.14.2 on Linux (4.4.0 x64) platform.

What's new
The compression format has been updated to xz which allows the decompression of the bootstrap.dat file while downloading it. If you are an expert you can use system pipes to inject the highly compressed serialized Bitcoin blockchain bootstrap.dat to the Bitcoin Core initial blockchain loadup process.

Setup
Move the decompressed bootstrap.dat into your Bitcoin-Qt application folder and (re)start your Bitcoin-Qt client:
  • Unix/Linux: ~/.bitcoin
  • MAC OS X: ~/Library/Application Support/Bitcoin/
  • Windows: [User Directory]AppDataRoamingBitcoin (i.e. C:UsersMyUsernameAppDataRoamingBitcoin

If you don't know how it works you can check the details on the download page.
Beware that after decompressing the XY file, you need additional ~130 GB to import the bootstrap file!


Download
--- https://goo.gl/gdHA8S ---

Hint
This is a private hosted download. To scope the hosting costs the download page requires a donation of whatever amount is suitable for you.
sr. member
Activity: 443
Merit: 251
Bitcoin Blockchain Download [bootstrap.dat]
[...]
Download
--- https://goo.gl/gdHA8S ---

Hint
This is a private hosted download. To scope the hosting costs the download page requires a donation of whatever amount is suitable for you.

It is no longer suggested to download the Bootstrap file anymore. It's better (and faster) to let the software download it and sync alone.
Yes, the recommended way is to sync the client alone.

But nevertheless an up-to-date bootstrap.dat file is useful for some usage scenarious like:
  • rolling out multiple installations
  • speeding up the initial sync (because the bootstrap.dat is already serialized)
staff
Activity: 3500
Merit: 6152
Bitcoin Blockchain Download [bootstrap.dat]

About
Code:
block date:     Sa. 08 Jul. 2017 14:17:11
block number:   #47480
file name:      bootstrap.dat.xz
file size:      ~80 GB [81,657 MB]
file format:    compressed xz (containing bootstrap.dat)
uncompressed:   ~116 GB

Indexed with Bitcoin Core v0.14.2 on Linux (4.4.0 x64) platform.

What's new
The compression format has been updated to xz which allows the decompression of the bootstrap.dat file while downloading it. If you are an expert you can use system pipes to inject the highly compressed serialized Bitcoin blockchain bootstrap.dat to the Bitcoin Core initial blockchain loadup process.

Setup
Move the decompressed bootstrap.dat into your Bitcoin-Qt application folder and (re)start your Bitcoin-Qt client:
  • Unix/Linux: ~/.bitcoin
  • MAC OS X: ~/Library/Application Support/Bitcoin/
  • Windows: [User Directory]AppDataRoamingBitcoin (i.e. C:UsersMyUsernameAppDataRoamingBitcoin

If you don't know how it works you can check the details on the download page.
Beware that after decompressing the XY file, you need additional ~130 GB to import the bootstrap file!


Download
--- https://goo.gl/gdHA8S ---

Hint
This is a private hosted download. To scope the hosting costs the download page requires a donation of whatever amount is suitable for you.

It is no longer suggested to download the Bootstrap file anymore. It's better (and faster) to let the software download it and sync alone.
sr. member
Activity: 443
Merit: 251
Bitcoin Blockchain Download [bootstrap.dat]

About
Code:
block date:     Sa. 08 Jul. 2017 14:17:11
block number:   #47480
file name:      bootstrap.dat.xz
file size:      ~80 GB [81,657 MB]
file format:    compressed xz (containing bootstrap.dat)
uncompressed:   ~116 GB

Indexed with Bitcoin Core v0.14.2 on Linux (4.4.0 x64) platform.

What's new
The compression format has been updated to xz which allows the decompression of the bootstrap.dat file while downloading it. If you are an expert you can use system pipes to inject the highly compressed serialized Bitcoin blockchain bootstrap.dat to the Bitcoin Core initial blockchain loadup process.

Setup
Move the decompressed bootstrap.dat into your Bitcoin-Qt application folder and (re)start your Bitcoin-Qt client:
  • Unix/Linux: ~/.bitcoin
  • MAC OS X: ~/Library/Application Support/Bitcoin/
  • Windows: [User Directory]AppDataRoamingBitcoin (i.e. C:UsersMyUsernameAppDataRoamingBitcoin

If you don't know how it works you can check the details on the download page.
Beware that after decompressing the XY file, you need additional ~130 GB to import the bootstrap file!


Download
--- https://goo.gl/gdHA8S ---

Hint
This is a private hosted download. To scope the hosting costs the download page requires a donation of whatever amount is suitable for you.
sr. member
Activity: 443
Merit: 251
Now, Blockchain requie over 120G, it too big for my PC,
other way to used Bitcore?

Usually you are not required to store the complete blockchain on your PC.
Did you consider to use pruning to reduce your storage requirements?

It's about adding a line "prune=[allowed blockchain storage in MB]" to your bitcoin.conf configuration file.
A value around 4488 [MB] which is currently about a month of backlog may be useful.
legendary
Activity: 2128
Merit: 1073
I tested the link plus installing it into new wallet on different PC, should work if you have winRAR
Yeah, I can confirm it "works", i.e. downloads in full and restores correctly.

The question is "how much effort is required to use it on a clean computer, especially Windows?" When somebody doesn't already have Google Chrome and payware RAR utility this isn't so easy.

Depending on the country the attempt to use of directory-level Google Drive link in Microsoft Internet Explorer one ends up with either a hang (described above) or a prompt to upgrade browser.

I don't know if payware RAR utility is smarter, but the freeware unrar restores those directories in a heavily fragmented state. It doesn't make sense for anyone to pay for full RAR license (or lookup the ever-popular cracks) when all that's required is a one-time uncompressing. With heavily fragmented store Bitcoin Core client works much slower then when it would do the download itself.

Yeah, but it makes everything go much faster, especially for users of the ISPs which don't have fully routable IP addresses but have to use to use CG-NAT-ed shared IP addresses. Google Drive doesn't seem to do per-IP throttling unlike e.g. Mega.nz .
sr. member
Activity: 652
Merit: 321
Apologies for that Dropbox link, they only allow a small of downloads per day. Trying Google drive now. *Bitcoin Blockchain Updated 10 Jun 17*

https://drive.google.com/file/d/0BzQX3WA9rhJCMERON0FFdUdhUkE/view?usp=drivesdk

Trying to help Bitcoin & get more nodes running to activate Segwit. These transaction fees are a killer!

If you run one of these clients https://uasf.bitcoinreminder.com/ you will start showing support for BIP148 UASF - before Activation on 1 Aug 17. The more people that run it the better the chance we have of getting Segwit. The power is in the users hands!

BTC: 14VbJUwQswTxf7VVn86nmqdseW7SjPh5FR
ETH: 0x600a9777936051daca6338b5fd397b546ea4313e

A small donation would be appreciated for cost of the cloud storage, however not necessary.

Please let me know how you go with that link.

I will leave this up as there's most likely going to be a need for 2 links with all the UASF traffic. Bitcoin is growing really fast.
sr. member
Activity: 652
Merit: 321
Does anyone require this link anymore? We currently have duplicates, probably not necessary.
Yours has a distinction of actually working. The one posted lkloon123 don't seem to work. They seem to hang on: Preparing download: zipping 1 file: progress circle gets stuck below 25%. In a dedicated Google Drive download utility they show as "files offline".

So maybe keep your until somebody confirms successful use of the other links?

Edit: Further research shows that barto123 posted hyperlink to a file, but lkloon123 posted link to a directory of subdirectories (named with a date) that contain the actual RAR files. Google Drive must have different special cases for different browsers. I managed to start download of lkloon123's post by starting it in "Google Internet Explorer Chrome", pausing the download and then copy-pasting the end-file link to a browser not approved by Google.

Pain in the neck, but it could be made to work. I'll update one the RAR download finishes and passes verification in unrar.

I tested the link plus installing it into new wallet on different PC, should work if you have winRAR
legendary
Activity: 2128
Merit: 1073
Does anyone require this link anymore? We currently have duplicates, probably not necessary.
Yours has a distinction of actually working. The one posted lkloon123 don't seem to work. They seem to hang on: Preparing download: zipping 1 file: progress circle gets stuck below 25%. In a dedicated Google Drive download utility they show as "files offline".

So maybe keep your until somebody confirms successful use of the other links?

Edit: Further research shows that barto123 posted hyperlink to a file, but lkloon123 posted link to a directory of subdirectories (named with a date) that contain the actual RAR files. Google Drive must have different special cases for different browsers. I managed to start download of lkloon123's post by starting it in "Google Internet Explorer Chrome", pausing the download and then copy-pasting the end-file link to a browser not approved by Google.

Pain in the neck, but it could be made to work. I'll update one the RAR download finishes and passes verification in unrar.
sr. member
Activity: 652
Merit: 321
Apologies for that Dropbox link, they only allow a small of downloads per day. Trying Google drive now. *Bitcoin Blockchain Updated 10 Jun 17*

https://drive.google.com/file/d/0BzQX3WA9rhJCMERON0FFdUdhUkE/view?usp=drivesdk

Trying to help Bitcoin & get more nodes running to activate Segwit. These transaction fees are a killer!

If you run one of these clients https://uasf.bitcoinreminder.com/ you will start showing support for BIP148 UASF - before Activation on 1 Aug 17. The more people that run it the better the chance we have of getting Segwit. The power is in the users hands!

BTC: 14VbJUwQswTxf7VVn86nmqdseW7SjPh5FR
ETH: 0x600a9777936051daca6338b5fd397b546ea4313e

A small donation would be appreciated for cost of the cloud storage, however not necessary.

Please let me know how you go with that link.

Does anyone require this link anymore? We currently have duplicates, probably not necessary.
member
Activity: 100
Merit: 10
I have uploaded the full blockchain to google drive
it's not the bootstrap file
choose the desired date and press download all

If the google drive server zipping proccess is slow, i will zip it first and upload next time.

for anyone who need it can go here
https://drive.google.com/drive/folders/0B8_47uQqNMc0NE00UWdRZ1VtSlE?usp=sharing

Will upload it weekly

if u would like to donate
BTC : 1Q28ZD2kKa8M4ix89PwPmzMJeiPw2HYHS9

-- updated --
latest update : 20/2/2017
legendary
Activity: 2128
Merit: 1073
Kinda newb here, but what's the purpose of this? Can't you simply download it the "normal" way? And I would imagine it would be hard to keep seeders seeding the torrent if you update it all the time.
The purpose is (mostly) to save time and (possibly) wear and tear on the storage hardware.

Bitcoin Core uses extremely primitive methods for maintaining the blockchain storage: it is quite slow and needlessly, extremely, write-intensive: to write effectively about 125GB of data to disk it will actually write multiple terabytes more in the process of internal reorganizations and pointless optimizations.

Good quality SSD devices have no problem handling it, but cheap eMMC or SD-card devices can be completely worn out before the initial synchronization finishes. Flash storage is always limited by the write endurance: how many times the storage cell can be erased and rewritten.
full member
Activity: 266
Merit: 100
Kinda newb here, but what's the purpose of this? Can't you simply download it the "normal" way? And I would imagine it would be hard to keep seeders seeding the torrent if you update it all the time.
member
Activity: 100
Merit: 10
I have uploaded the full blockchain to google drive
it's not the bootstrap file
choose the desired date and press download all

If the google drive server zipping proccess is slow, i will zip it first and upload next time.

for anyone who need it can go here
https://drive.google.com/drive/folders/0B8_47uQqNMc0NE00UWdRZ1VtSlE?usp=sharing

Will upload it weekly

if u would like to donate
BTC : 1Q28ZD2kKa8M4ix89PwPmzMJeiPw2HYHS9

Zip file included, u can choose which to download Cheesy
newbie
Activity: 7
Merit: 0
I have uploaded the full blockchain to google drive
it's not the bootstrap file
choose the desired date and press download all

If the google drive server zipping proccess is slow, i will zip it first and upload next time.

for anyone who need it can go here
https://drive.google.com/drive/folders/0B8_47uQqNMc0NE00UWdRZ1VtSlE?usp=sharing

Will upload it weekly

if u would like to donate
BTC : 1Q28ZD2kKa8M4ix89PwPmzMJeiPw2HYHS9

Hey! Thanks for that! Just got mine corrupted yesterday and needed to download it again. I will be seeding this till you upload a new one.
member
Activity: 100
Merit: 10
I have uploaded the full blockchain to google drive
it's not the bootstrap file
choose the desired date and press download all

If the google drive server zipping proccess is slow, i will zip it first and upload next time.

for anyone who need it can go here
https://drive.google.com/drive/folders/0B8_47uQqNMc0NE00UWdRZ1VtSlE?usp=sharing

Will upload it weekly

if u would like to donate
BTC : 1Q28ZD2kKa8M4ix89PwPmzMJeiPw2HYHS9
legendary
Activity: 2128
Merit: 1073
Please don't listen to bullshit from non-technical people. Bitcoin Core does initial download faster only in certain conditions, that nowadays could be considered laboratory-like. With the real user environments (especially technical newbies or people outside USA) it is much more reliable and oftentimes faster to do this using Bittorrent or cloud file storage.
This is simply untrue.

Unless your internet connection is very slow the vast majority of time is spent in validation and data handling even on a 24 core host.  

If you download separately you cannot overlap the download and validation.  So unless your download is nearly infinitely fast it must be slower.

This experiment is conducted regularly in real conditions at least with every release (since we benchmark for synchronization performance regressions).
Dude, you are so disconnected from reality that it isn't funny anymore.

Your "real conditions" consist of:

1) Not running Windows natively on the hardware as a matter of core dev team policy, but on virtualized high-end hardware.

2) Using well tested hardware, probably with ECC RAM and SSD storage.

3) Using static (or nearly static) IPv4 address that isn't shared with other users of the ISP providing cabled/fixed service.

The real users' conditions are vastly different:

1) Windows running natively, frequently on cheap computers or external drives connected with USB.

2) Untested hardware that had never run any sort of database application, only web browsers and games. Most users will try to put Bitcoin on a mechanical drive and to compound problems will run various online anti-virus and other lame security applications.

3) Outside of the USA static IPv4 are quite rare commodity, most users have either forcibly changed dynamic IPv4, shared IPv4 through CG-NAT or dual-stack-lite IPv6 deployments where only IPv6 is static and IPv4 is shared. Large fraction of Bitcoin users use various non-cabled ISPs either radio-line or cellular. Bittorrent deals with those much better than Bitcoin Core.

4) In practice the beginning users have to attempt initial synchronization several times until their resolve problems with their configuration following the usual recipe: blow away everything except wallet.dat and restart from scratch, very much in the days of MS-DOS on a PC-compatible. Downloading the data separately at least allows them to start cleanly in an reproducible configuration that allows sensible troubleshooting.

5) For many users the proper metric to optimize is not "minimum total time" but "minimum total costs". Especially those users on non-cabled ISPs have non-metered, well-performing connections only through 8 to 12 hours during night time. For them separating download (via Bittorrent or cloud file locker) and local synchronization makes obvious sense.
 
created with multiple restarts of the Bitcoin client, needlessly keep track of orphaned blocks, keep track of transactions in somebody's wallet, etc.
Orphaned blocks are about 1% -- who cares if there is 1% of overhead in the files?  The linearize tool in the contribs directory will create block files without them-- sure, but they're not a big deal. The main reason to exclude them is to get a reproducible file.  The wallet _never_ has any effect on the content of the block files.

The risk with copying a chainstate, beyond the risk of being tricked onto a fork where the attacker has created a bunch of coins out of thin air is that the leveldb database files are not a safe external interface and it may well be possible to get remote code execution with a specially crafted database.  BDB (used for the wallets) can easily be caused to crash with out of bounds memory accesses from crafted database files, for example.

I'm pretty sure that that a UTXO assume-valid type sync will be supported (even a default) in the future-- but that doesn't mean that copying database files from third parties is safe-- personally I'd never do it.
It isn't the 1% waste that is the problem. It is lack of reproducibility and lack of possibility of making sensible incremental backups and incremental synchronization amongst multiple machines.

Your paranoia is largely unfounded for two reasons:

1) even if you (or your friends stateside) don't know the providers of pre-initialized state directories, those people are frequently quite well-known outside of the USA and can be reasonably trusted.

2) most of the users desiring shortcuts to initialize don't have any coins in their wallet and don't plan on putting any just yet. They are planning on learning or demonstrating the technology.

3) the "crafted leveldb exploit to put user on a fake fork" is largely theoretical so far, whereas the practical exploits were social engineering related to fraudulent technical help with extremely fragile and problematic Bitcoin Core that has almost no internal RAS features (reliability - availability - serviceability) and laughable error messages like "there was checksum error, aborting".

Don't even get me started on using sensible storage architecture for Bitcoin Core. I tried to explain the benefits of storage layer abstraction to etotheipi in 2013:

https://bitcointalksearch.org/topic/new-blockchain-management-in-armory-144015

His position was that he rather have his company fail than use a database engine that is more than an educational toy. By the time they tried to switch to LightningDB he was out of money and out of patience from the prospective enterprise customers.
legendary
Activity: 4214
Merit: 1313
Please don't listen to bullshit from non-technical people. Bitcoin Core does initial download faster only in certain conditions, that nowadays could be considered laboratory-like. With the real user environments (especially technical newbies or people outside USA) it is much more reliable and oftentimes faster to do this using Bittorrent or cloud file storage.
This is simply untrue.

Unless your internet connection is very slow the vast majority of time is spent in validation and data handling even on a 24 core host. 

If you download separately you cannot overlap the download and validation.  So unless your download is nearly infinitely fast it must be slower.

This experiment is conducted regularly in real conditions at least with every release (since we benchmark for synchronization performance regressions).

Finally. Maybe this time these downloads are finally debunked and a bunch of people stop wasting their time.

Doubtful. 😀  Given the same thing has been said for several years now and makes no difference.  Lol
legendary
Activity: 1512
Merit: 1012
Please don't listen to bullshit from non-technical people. Bitcoin Core does initial download faster only in certain conditions, that nowadays could be considered laboratory-like. With the real user environments (especially technical newbies or people outside USA) it is much more reliable and oftentimes faster to do this using Bittorrent or cloud file storage.
This is simply untrue.

Unless your internet connection is very slow the vast majority of time is spent in validation and data handling even on a 24 core host. 

If you download separately you cannot overlap the download and validation.  So unless your download is nearly infinitely fast it must be slower.

This experiment is conducted regularly in real conditions at least with every release (since we benchmark for synchronization performance regressions).

Finally. Maybe this time these downloads are finally debunked and a bunch of people stop wasting their time.
Pages:
Jump to: