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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1XGTzt-0005zN-F8
for Bitcoin-development@lists.sourceforge.net;
Sun, 10 Aug 2014 14:21:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.213.173 as permitted sender)
client-ip=209.85.213.173; envelope-from=jgarzik@bitpay.com;
helo=mail-ig0-f173.google.com;
Received: from mail-ig0-f173.google.com ([209.85.213.173])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XGTzs-0003La-Ep
for Bitcoin-development@lists.sourceforge.net;
Sun, 10 Aug 2014 14:21:21 +0000
Received: by mail-ig0-f173.google.com with SMTP id h18so3098739igc.6
for <Bitcoin-development@lists.sourceforge.net>;
Sun, 10 Aug 2014 07:21:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=5DI7LcLR8mfTx1ovrnT+prZ11UpwXbvC7eESpOLO0NE=;
b=m4Iq9mUbg/Le8RJmTbYRF1tnZpcwIo33TfvuEXHcSdfURKrt/UkJld/7Og/NwN9G6C
1KLq4fVsnTBmF1gwaZ82+AppeHSe5KfVLSlRJJ1vLNLSm8pR9lisZLL19nsnOYI5VEGc
qPlzWgT+qXEhGQNDuldVA8rfL8nbN4XxF4kPyV2jJV+scDseXD8dvQJjwcC5WIEV61ZK
5XSbSY+00BuB4iY8F3+OcQ1ug8NZBhfNqnZWOxcn0d0+NCm8DcVbX12CwECVK3aas1pP
TxhIqgvIgr434FijKg/nPYbF10MgEccgEHRW00eryjaxz3vpSkqsUeapJ47Y//e+6dqD
xH6w==
X-Gm-Message-State: ALoCoQk4CuBzMcciXc2cRFt9K6BMa7UaPfyBl52jEGWmddZu9Q8f/EEmptmzSuTBni0CKiTG+KP8
X-Received: by 10.50.178.172 with SMTP id cz12mr22119331igc.22.1407680475060;
Sun, 10 Aug 2014 07:21:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.10.78 with HTTP; Sun, 10 Aug 2014 07:20:54 -0700 (PDT)
In-Reply-To: <53E776D1.1010503@bitwatch.co>
References: <53E776D1.1010503@bitwatch.co>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Sun, 10 Aug 2014 10:20:54 -0400
Message-ID: <CAJHLa0MPe-Sb_Lf_+rrcFTSsVAwBJROQNMDbTRg3eqWJtCd0pw@mail.gmail.com>
To: "mbde@bitwatch.co" <mbde@bitwatch.co>
Content-Type: text/plain; charset=UTF-8
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 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: 1XGTzs-0003La-Ep
Cc: Bitcoin Dev <Bitcoin-development@lists.sourceforge.net>
Subject: Re: [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 14:21:21 -0000
This issue is being worked on, under the category of "headers first
synchronization."
Until that is finished, it is recommended that you download
bootstrap.dat via torrent:
https://bitcointalk.org/index.php?topic=145386.0
On Sun, Aug 10, 2014 at 9:42 AM, mbde@bitwatch.co <mbde@bitwatch.co> wrote:
> 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)
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
