You've already forked nakamoto-archive
wakgill
31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
---
|
|
layout: forum
|
|
title: 'Re: Bitcoin 0.3.2 released'
|
|
grand_parent: Forum Posts
|
|
parent: Bitcoin Forum
|
|
nav_order: 231
|
|
date: 2010-07-17 22:54:24 UTC
|
|
original: https://bitcointalk.org/index.php?topic=437.msg3825#msg3825
|
|
---
|
|
|
|
# Re: Bitcoin 0.3.2 released
|
|
---
|
|
|
|
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight">
|
|
<code>Re: Bitcoin 0.3.2 released
|
|
July 17, 2010, 10:54:24 PM
|
|
|
|
<a href="https://bitcointalk.org/index.php?topic=437.msg3810#msg3810">Quote from: llama on July 17, 2010, 09:56:25 PM</a>
|
|
-------------
|
|
However, it's important that you don't lock all the way up the very latest block. Otherwise, the attacker could generate a fake block (or a few) right before you happen to lock it, and then his attack would be far easier than it would have been without the block lock.
|
|
-------------
|
|
|
|
I went about 200 blocks back. The block chain was a clean straight line without branches, and there was only one known version of the locked block.
|
|
|
|
<a href="https://bitcointalk.org/index.php?topic=437.msg3810#msg3810">Quote from: llama on July 17, 2010, 09:56:25 PM</a>
|
|
-------------
|
|
Also, I'm assuming that the block lock means that the blocks will also come prepackaged with the client. Is this so?
|
|
-------------
|
|
|
|
Sorry, not yet, but I do want to make the initial block download faster.</code></pre></div></div>
|