blob: 88744f013c6be4196377d33bce92f17edbea79ab (
plain)
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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mbde@bitwatch.co>) id 1XGTOf-0006kZ-9s
for Bitcoin-development@lists.sourceforge.net;
Sun, 10 Aug 2014 13:42:53 +0000
Received: from dd32718.kasserver.com ([85.13.150.64])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1XGTOd-0002F8-Jn
for Bitcoin-development@lists.sourceforge.net;
Sun, 10 Aug 2014 13:42:53 +0000
Received: from [192.168.100.28]
(dslb-084-059-055-227.084.059.pools.vodafone-ip.de [84.59.55.227])
by dd32718.kasserver.com (Postfix) with ESMTPSA id ABBC5490017E
for <Bitcoin-development@lists.sourceforge.net>;
Sun, 10 Aug 2014 15:42:44 +0200 (CEST)
Message-ID: <53E776D1.1010503@bitwatch.co>
Date: Sun, 10 Aug 2014 15:42:41 +0200
From: "mbde@bitwatch.co" <mbde@bitwatch.co>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1XGTOd-0002F8-Jn
Subject: [Bitcoin-development] Synchronization: 19.5 % orphaned blocks at
height 197'324
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: Sun, 10 Aug 2014 13:42:53 -0000
Hello all,
I'm currently synchronizing a new node and right now, at a progress of a
height of 197'324 blocks, I count in my debug.log an aweful amount of
38'447 orphaned blocks which is about 19.5 %.
It has been I while since I watched the synchronization process closely,
but this number seems pretty high to me.
I'm wondering about the following: would it be possible for a malicious
party to generate chains of blocks with low difficulity which are not
part of the main chain to slow down the sync process?
Build and version information:
https://github.com/jmcorgan/bitcoin/tree/026686c7de76dfde6fcacfc3d667fb3418a946a7
(sipa/jmcorgan address index)
Rebased with:
https://github.com/bitcoin/bitcoin/tree/94e1b9e05b96e4fe639e5b07b7a53ea216170962
(almost up-to-date mainline)
Compressed debug.log attached:
https://www.dropbox.com/s/uvtd91xiwmdmun7/debug.7z?m=
(filesize: 7.67 MB, uncompressed: 41.3 MB)
|
