Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMo <div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1931.msg24438#msg24438">Quote from: satoshi on November 25, 2010, 05:51:39 PM</a></div><div class="quote">It's not the downloading that takes the time, it's verifying and indexing it.<br/></div><br/>This is not true of many novice users, who say things like "well it took several hours to catch all the 90 000 blocks but finally it arrived" (quoted from one new user, on IRC, today).<br/><br/><div class="quoteheader">Quote</div><div class="quote">Bandwidthwise, it's more efficient than if you downloaded an archive.<br/></div><br/>Agreed. &nbsp;Compressed in an archive, blk0001.dat is around 36MB.<br/><br/><div class="quoteheader">Quote</div><div class="quote">Bitcoin only downloads the data in blk0001.dat, which is currently 55MB, and builds blkindex.dat itself, which is 47MB. &nbsp;Building blkindex.dat is what causes all the disk activity.<br/><br/>During the block download, it only flushes the database to disk every 500 blocks. &nbsp;You may see the block count pause at ??499 and ??999. &nbsp;That's when it's flushing.<br/></div><br/>It remains the download, not the verification, that has the highest <i>variability of experience</i>, where first time users see a delay of 30 minutes to <b>several hours</b> before the software is actually usable. &nbsp;Some P2P nodes may be extremely slow (I see high variability in latency and throughput for old blocks, and blocks larger than 512 bytes). &nbsp;End user bandwidth may be low, spotty or expensive. &nbsp;Firewalls are often a problem.<br/><br/>I'm betting that the above complaint from a new user was due to a Microsoft firewall; but the point stands:&nbsp; large variance of network configuration and capability implies the P2P download impact <i>may be</i> far, far greater than impact of on-disk verification of 90,000 blocks.<br/><br/><div class="quoteheader">Quote</div><div class="quote">Doing your own verifying and indexing is the only way to be sure your index data is secure. &nbsp;If you copy blk0001.dat and blkindex.dat from an untrusted source, there's no way to know if you can trust all the contents in them.<br/></div><br/>Who said untrusted? &nbsp;The proposal is that you distribute blk0001.dat (and only blk0001.dat) in the bitcoin.org official client downloads. &nbsp;And of course the client will spend some time verifying blk0001.dat upon first use. &nbsp;This is unavoidable, and nobody has proposed changing or eliminating verification.<br/><br/>Just shipping blk0001.dat with official bitcoin would eliminate several headaches that new bitcoin users continue to experience.<br/></div> text/html