1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1R0fz4-00048L-IL
for bitcoin-development@lists.sourceforge.net;
Mon, 05 Sep 2011 20:41:34 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.47 as permitted sender)
client-ip=209.85.214.47; envelope-from=gavinandresen@gmail.com;
helo=mail-bw0-f47.google.com;
Received: from mail-bw0-f47.google.com ([209.85.214.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R0fz3-0003bM-LJ
for bitcoin-development@lists.sourceforge.net;
Mon, 05 Sep 2011 20:41:34 +0000
Received: by bkbzu17 with SMTP id zu17so6751586bkb.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 05 Sep 2011 13:41:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.153.16 with SMTP id i16mr2491267bkw.46.1315255287167; Mon,
05 Sep 2011 13:41:27 -0700 (PDT)
Received: by 10.204.58.135 with HTTP; Mon, 5 Sep 2011 13:41:24 -0700 (PDT)
Date: Mon, 5 Sep 2011 16:41:24 -0400
Message-ID: <CABsx9T2vS4a3k6_6T7KvA+eoc8Rc61HGKRc0nBVMqLeGeTPftQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1R0fz3-0003bM-LJ
Subject: [Bitcoin-development] Pull request: faster initial blockchain
download
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 05 Sep 2011 20:41:34 -0000
I'd appreciate review/feedback on this:
https://github.com/bitcoin/bitcoin/pull/492
This change skips ECDSA signature verification for transactions during
the initial block-chain download, which makes downloading the block
chain much faster.
"Initial block chain download" is all blocks up to 120 blocks before
the last blockchain lock-in point.
Reasoning for why this is safe:
If an attacker tries to feed a client bad transactions during the
initial block-chain download (transactions with invalid signatures),
then they change the merkle tree, and at the first blockchain lock-in
the bad chain will be rejected.
Transactions are still checked for orphan blocks that come in during
initial block-chain-download (ConnectInputs will be called with
fBlock=FALSE) and for mined blocks (ConnectInputs called with
fMiner=TRUE).
--
--
Gavin Andresen
|
