A torrent has been around for a while:
[BETA] Bitcoin blockchain torrent
https://bitcointalksearch.org/topic/beta-bitcoin-blockchain-torrent-117982
Topic: Bitcoin Block Chain Download (Read 16437 times)
been meddling with blockchain loading for several days,
inside VM and natively, got hdd overstuffing and
blockchan/index file damaged and all.
afterall i got 193000 checkpoint and topped it to last of 2013-JAN-30
6.5GB ain't no joke
anywayz, here my magnet is:
magnet:?xt=urn:btih:A501B62BEA0265413D76C58663BD0522D0FE91BE&dn=BLK-2013-01-30&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce
sure it's no top security, but might help someone
feedback appreciated, someone might use uTorrent 'rehash' option to validate blk0001.dat, blk0002.dat, blk0003.dat
those are append-only ( not sure if blkindex.dat might be compared, try it too and post match % )
cheers
ps: if you keep those on NTFS, try 'compress' flag.
it gives me 0.57 GiB down, 6.46 to 5.89
inside VM and natively, got hdd overstuffing and
blockchan/index file damaged and all.
afterall i got 193000 checkpoint and topped it to last of 2013-JAN-30
6.5GB ain't no joke
anywayz, here my magnet is:
magnet:?xt=urn:btih:A501B62BEA0265413D76C58663BD0522D0FE91BE&dn=BLK-2013-01-30&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce
sure it's no top security, but might help someone
feedback appreciated, someone might use uTorrent 'rehash' option to validate blk0001.dat, blk0002.dat, blk0003.dat
those are append-only ( not sure if blkindex.dat might be compared, try it too and post match % )
cheers
ps: if you keep those on NTFS, try 'compress' flag.
it gives me 0.57 GiB down, 6.46 to 5.89
I wish your host works
Is there any other site that hosts (regularly updated) blockchain files? I tried using bootstap.dat, but that still leaves ~17k blocks to download, and those take forever.
Read the post in this thread, immediately preceding yours
I must be missing something. The link in Matt's post points to a bootstrap.dat file. That contains the first 193k blocks, which leaves the last 17k to be downloaded. I have taken that route and after 6 hours I'm still 15k blocks short, so I'm looking for a way to get the complete (or almost complete) blockchain.
Is there any other site that hosts (regularly updated) blockchain files? I tried using bootstap.dat, but that still leaves ~17k blocks to download, and those take forever.
Read the post in this thread, immediately preceding yours
Is there any other site that hosts (regularly updated) blockchain files? I tried using bootstap.dat, but that still leaves ~17k blocks to download, and those take forever.
In the interest of convincing people to update their bookmarks, because this thread pops up high on google results, and because http://bitcoin.bluematt.me/bitcoin-nightly/blockchain-nightly/ has been down for a year+ now:
Please update your bookmarks to tcatm's chain at http://eu1.bitcoincharts.com/blockchain/
Please update your bookmarks to tcatm's chain at http://eu1.bitcoincharts.com/blockchain/
Correct. For the bogus block chain to be useful the attacker would also need to ioslate your node to feed you "false blocks". I think the security risk isn't that great but given the blockchain is the cornerstone of the network it likely isn't a good idea to take chances.
I do think the network could use a concept like "macro blocks". For old blocks (say older than 5000 blocks) the protocol could have all nodes take 10,000 block segments, compress them and take a hash. New nodes could request a macro block, download it from multiple peers (or even static websites/repositories/mirrors) and then request a hash for the blocks from nodes. If your nodes gets same hash from multiple nodes and it matches the "macro block" then the macro block is valid.
I do think the network could use a concept like "macro blocks". For old blocks (say older than 5000 blocks) the protocol could have all nodes take 10,000 block segments, compress them and take a hash. New nodes could request a macro block, download it from multiple peers (or even static websites/repositories/mirrors) and then request a hash for the blocks from nodes. If your nodes gets same hash from multiple nodes and it matches the "macro block" then the macro block is valid.
AWESOME! BIP-it!
Correct. For the bogus block chain to be useful the attacker would also need to ioslate your node to feed you "false blocks". I think the security risk isn't that great but given the blockchain is the cornerstone of the network it likely isn't a good idea to take chances.
I do think the network could use a concept like "macro blocks". For old blocks (say older than 5000 blocks) the protocol could have all nodes take 10,000 block segments, compress them and take a hash. New nodes could request a macro block, download it from multiple peers (or even static websites/repositories/mirrors) and then request a hash for the blocks from nodes. If your nodes gets same hash from multiple nodes and it matches the "macro block" then the macro block is valid.
I do think the network could use a concept like "macro blocks". For old blocks (say older than 5000 blocks) the protocol could have all nodes take 10,000 block segments, compress them and take a hash. New nodes could request a macro block, download it from multiple peers (or even static websites/repositories/mirrors) and then request a hash for the blocks from nodes. If your nodes gets same hash from multiple nodes and it matches the "macro block" then the macro block is valid.
Sorry for opening up an old thread, but I think the above needs to be cleared up. Is it really possible?
Any attacker wishing to forge a block chain will never be able to make a chain with a total amount of work performed that is greater than the network (unless he has more processing power than the network). Thus, when the client with the supposedly illegitimate block chain connects to other nodes and receives a new block, the fake block chain will be orphaned and the real block chain will be received, right? I mean, how can one get around - for one - the 'work' measure (which proves how much work has been spent creating a chain) and secondly the prev_hash field which will not match when a new block is announced in the network?
Any attacker wishing to forge a block chain will never be able to make a chain with a total amount of work performed that is greater than the network (unless he has more processing power than the network). Thus, when the client with the supposedly illegitimate block chain connects to other nodes and receives a new block, the fake block chain will be orphaned and the real block chain will be received, right? I mean, how can one get around - for one - the 'work' measure (which proves how much work has been spent creating a chain) and secondly the prev_hash field which will not match when a new block is announced in the network?
What harm could occur from using a bad block chain from a malicious source?
Because it isn't verified, a malicious user could literally give themselves a large balance that your client would then accept. They can also change other balances. Worst of all, they can permanently put you on their own fork of the blockchain. Basically, if you download this, you must implicitly trust the person as much as you'd trust the person who built the bitcoin client you are currently using.
Unfortunately, using a block-chain that you downloaded yourself seems to be broken or unsupported currently. I posted about using a downloaded block-chain on OS X, but no solution has yet been found.
I just downloaded the newest blockchain today and i put it in userfile\application data\bitcoin then opened bitcoin and nothing has changed except the number of blocks isnt changing anymore. i went to the bitcoin faucet and put in my address code and it said it sent but i still havent gotten anything. did i do something wrong? i just started with this yesterday so im completely clueless on this sorry.
In theory you could verify the validity of this blockchain by downloading it and installing it in an empty bitcoin client, then connecting your real bitcoin client to the empty client using the -connect switch - it'll download and verify the blockchain over whatever speed the connection between the two computers are... but it's a hassle...
It's a pity the -rescan command doesn't validate the block chain.
Will
It's a pity the -rescan command doesn't validate the block chain.
Will
What harm could occur from using a bad block chain from a malicious source?
No thanks, I'd rather download it myself. My money is at stake here, after all.
For some, it can take hours for the block chain to download over p2p
also I have provided notice on the site that It is recommend to download the Block Chain from http://bitcoin.bluematt.me/bitcoin-nightly/blockchain-nightly/ instead
I will still provide the download link, and the auto updater will still run (never hurts to have another mirror)
also I have provided notice on the site that It is recommend to download the Block Chain from http://bitcoin.bluematt.me/bitcoin-nightly/blockchain-nightly/ instead
I will still provide the download link, and the auto updater will still run (never hurts to have another mirror)
What's the need to download the blockchain anyway?
Agree -- please download from bluematt's repository or https://sourceforge.net/projects/bitcoin/files/OldFiles/
As Maged indicated, if you download the block chain outside of P2P, the block chain will not be verified and could potentially be quite wrong. Users are urged to avoid the download provided by the OP.
Jump to: