Pages:
Author

Topic: [ANN] Bitcoin blockchain data torrent - page 9. (Read 211194 times)

legendary
Activity: 2618
Merit: 1007
August 31, 2014, 03:42:53 PM
I'm having some trouble getting the 22.5 GB file. I have the 21GB which appears to be from last April. I tried using the torrent link from the OP as well as manually adding the infohash. They both lead me to the 21 GB file. Any thought as to what I'm doing wrong?

22500000 bytes are approx. 21 GiB (1024 bytes = 1 GiB), so if your client displays "21 GB", it is already the new file.
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
August 31, 2014, 03:10:02 PM
How much time I need to sync the blockchain from zero using bitcoin-qt and how much with torrent?
I have a 7mb adsl.

It took me 3 days with a 100MBit connection with bitcoin-core. As has been said: you sync only with one client, if you are lucky they have a fast connection. With the torrent you will use your line at ~90% (keep 10% for orga/surfing) or even fully*. It went up to  When you are done keep seeding to help others.

* Edit: just did a test. The torrent runs at ~ 24MBit/s after ~30 seconds. bitcoin-core is never going to achieve that rate.
newbie
Activity: 28
Merit: 0
August 31, 2014, 11:32:35 AM
I'm downloading. Thank you all. It looks like a lot of time saved using them for more than a pc.
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
August 31, 2014, 04:52:58 AM
How much time I need to sync the blockchain from zero using bitcoin-qt and how much with torrent?
I have a 7mb adsl.

Downloading bootstrap.dat will take some hours and syncing will take a few hours more. Smiley It might go upto 1-2 days.

~~MZ~~
legendary
Activity: 1596
Merit: 1100
August 30, 2014, 03:54:19 PM
i still think the new torrent link is incorrect.

Can you be more specific?  Which link is incorrect?

newbie
Activity: 28
Merit: 0
August 30, 2014, 03:04:43 PM
How much time I need to sync the blockchain from zero using bitcoin-qt and how much with torrent?
I have a 7mb adsl.
newbie
Activity: 2
Merit: 0
August 30, 2014, 02:47:18 PM
i still think the new torrent link is incorrect.
legendary
Activity: 1974
Merit: 1029
August 30, 2014, 09:24:46 AM
I am confused, what is this data used for? Is this even useful? How can we benefit from it?

If you're setting up a new full node, it's faster to get the blockchain via torrent (and then let bitcoin core import and validate it) than to let bitcoin core download it by itself. This is because bitcoin core currently downloads from one peer at once, which isn't optimal.
member
Activity: 92
Merit: 10
August 30, 2014, 08:46:32 AM
I am confused, what is this data used for? Is this even useful? How can we benefit from it?
newbie
Activity: 2
Merit: 0
August 30, 2014, 07:57:30 AM
I'm having some trouble getting the 22.5 GB file. I have the 21GB which appears to be from last April. I tried using the torrent link from the OP as well as manually adding the infohash. They both lead me to the 21 GB file. Any thought as to what I'm doing wrong?
donator
Activity: 335
Merit: 250
Bitcoin, Ripple & Blockchain pioneer
August 29, 2014, 09:13:56 AM
Future torrents will include the block chain split into multiple files, never exceeding 1GB in size.

I agree 100% with this choice, it does not make any sense to have a large file when smaller ones are easier to manage.

This way, people that already has the first blocks can skip those ones and let their bittorrent client only download the last ones.

Armory already downloads the blockchain through bittorrent by default, I wish the bitcore core client start doing it as well, until that moment you can count on me seeding this torrent manually for everyone at any time.
legendary
Activity: 1596
Merit: 1100
August 27, 2014, 10:26:18 AM
Thanks for double-checking my work!
newbie
Activity: 3
Merit: 0
August 26, 2014, 07:44:19 PM
Torrent officially updated!  See OP.  New height:  317,000 @ 22.5 GB

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:

Code:
$ ./blockheight -e 295000 d83ea8602fb5d2ad863afc7fae1b25794bc7da37d2da642e6aca15f2ad19d9e9  -
$ for((i = 0; i < 295001; i++)); do  ./bitcoin-cli getblock `./bitcoin-cli getblockhash $i` false ; done | sha256sum
d83ea8602fb5d2ad863afc7fae1b25794bc7da37d2da642e6aca15f2ad19d9e9  -

Blocks 295001 through 313000, bootstrap matches blockchain:

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

Blocks 313001 through 317000, bootstrap matches blockchain:

Code:
$ ./blockheight -s 313001 < bootstrap-317000.dat | sha256sum
a4ab78b82bb7b75b640a6f128fd66cb911362aa8058ebf574b4e02c111f63ba5  -
$ for((i = 313001; i < 317001; i++)); do  ./bitcoin-cli getblock `./bitcoin-cli getblockhash $i` false ; done | sha256sum
a4ab78b82bb7b75b640a6f128fd66cb911362aa8058ebf574b4e02c111f63ba5  -
staff
Activity: 1286
Merit: 1085
August 25, 2014, 06:52:26 AM
I agree keeping the process automagically performed is better for new users.

Absolutely. Using a torrent at all is a hack and a (small) barrier to entry that should be removed if possible.

But if using a torrent is the current plan I can throw bandwidth at it.

There seem to be more downloaders than seeders on the new torrent right now. After changing torrents I'm downloading at 0kB/s and uploading at 1 MB/s.


If you already have the blockchain you should generate the file using the auxiliary script linearize.py instead of downloading it through the torrent (it is faster than downloading it and doesn't hurt the ones already seeding it, leaving bandwith for the ones who really need to download it).

Despite of that, it is good to have more seeders indeed.

Thanks,


Adriano
sd
hero member
Activity: 730
Merit: 500
August 25, 2014, 02:38:28 AM
I agree keeping the process automagically performed is better for new users.

Absolutely. Using a torrent at all is a hack and a (small) barrier to entry that should be removed if possible.

But if using a torrent is the current plan I can throw bandwidth at it.

There seem to be more downloaders than seeders on the new torrent right now. After changing torrents I'm downloading at 0kB/s and uploading at 1 MB/s.
staff
Activity: 1286
Merit: 1085
August 24, 2014, 08:36:00 AM
As far as I understood it, bootstrap.dat gets loaded automatically while with "-reindex" people need to know how to add something to a command line. I am not sure if this is not causing more issues for more people than the ones trying to run Bitcoin-Core on some ancient hardware.

Also Bitcoin-Core could prompt the user after importing from bootstrap.dat to delete the file, to combat the "double space taken" issue. I'd at least like to see both approaches continued until Bitcoin-Core finally is capable of downloading blocks from more than one source, then this whole thing can be discontinued anyways.

I agree keeping the process automagically performed is better for new users.

How about include an empty file (flag file) in the torrent which only purpose is to indicate to the bitcoin daemon/wallet run the reindex process (the daemon/wallet would automatically remove this file after the reindex process is done) ?

Adriano
legendary
Activity: 2618
Merit: 1007
August 24, 2014, 03:46:31 AM
As far as I understood it, bootstrap.dat gets loaded automatically while with "-reindex" people need to know how to add something to a command line. I am not sure if this is not causing more issues for more people than the ones trying to run Bitcoin-Core on some ancient hardware.

Also Bitcoin-Core could prompt the user after importing from bootstrap.dat to delete the file, to combat the "double space taken" issue. I'd at least like to see both approaches continued until Bitcoin-Core finally is capable of downloading blocks from more than one source, then this whole thing can be discontinued anyways.
legendary
Activity: 1596
Merit: 1100
August 23, 2014, 09:40:06 PM
Note:  For a minority of users, the bootstrap.dat "one huge 20GB file" import method does not work beyond 4GB of data.  This is due to some limitations with large files on some 32-bit operating systems.  It is planned to move away from a single bootstrap.dat file to a directory full of blkNNNNN.dat files that may be imported directly into bitcoind via "-reindex".  The bootstrap.dat file also causes a 2x disk space increase over the "-reindex" method, which occasionally triggers complaints from users on low disk space cloud servers.

For these reasons, bootstrap.dat import method is being deprecated (at least with regards to this torrent).  Today's torrent update will be the last bootstrap.dat torrent.

Future torrents will include the block chain split into multiple files, never exceeding 1GB in size.


legendary
Activity: 1596
Merit: 1100
August 23, 2014, 06:49:30 PM
Torrent officially updated!  See OP.  New height:  317,000 @ 22.5 GB
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
August 21, 2014, 05:28:44 AM
See in linearize log, in my case it crashes on rpc timeout sometimes.
I has change timeout in code and run linearize as nice Smiley
Pages:
Jump to: