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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1R3VJN-0005xv-J7
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Sep 2011 15:54:13 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.47 as permitted sender)
client-ip=209.85.213.47; envelope-from=witchspace81@gmail.com;
helo=mail-yw0-f47.google.com;
Received: from mail-yw0-f47.google.com ([209.85.213.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R3VJJ-0003GR-UK
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Sep 2011 15:54:13 +0000
Received: by ywf7 with SMTP id 7so679227ywf.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 13 Sep 2011 08:54:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.196.18 with SMTP id t18mr2757294ybf.349.1315929244457;
Tue, 13 Sep 2011 08:54:04 -0700 (PDT)
Received: by 10.151.107.13 with HTTP; Tue, 13 Sep 2011 08:54:04 -0700 (PDT)
In-Reply-To: <CABsx9T2XLj4gZVPYodteaVCm0chR1n4WLUoSqB6+NnmWCDqHKQ@mail.gmail.com>
References: <CABsx9T2XLj4gZVPYodteaVCm0chR1n4WLUoSqB6+NnmWCDqHKQ@mail.gmail.com>
Date: Tue, 13 Sep 2011 15:54:04 +0000
Message-ID: <CAJNQ0svCL-0m_xxDWLtfE=LSWJyZ_xR0VABGBaBhDEWKzvZxnQ@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd487cc2a5a9904acd4a720
X-Spam-Score: -0.5 (/)
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
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
1.0 HTML_MESSAGE BODY: HTML included in message
-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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R3VJJ-0003GR-UK
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Difficulty adjustment / time issues
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: Tue, 13 Sep 2011 15:54:13 -0000
--000e0cd487cc2a5a9904acd4a720
Content-Type: text/plain; charset=ISO-8859-1
> Fixing (2) is easier; incorporating a ntp library and/or simply
> removing the bitcoin mining code from the client but requiring pools
> and miners to have accurate-to-within-a-minute system clocks (or their
> blocks will be "discouraged") seems reasonable to me.
Incorporating NTP seems overkill. Most OSes come with NTP support integrated
these days (even XP did?), there is no excuse to not be running it,
especially on a server.
If you want to
> produce blocks that the rest of the network will accept, run ntp on
> your system.
>
Requiring it for miners sounds very reasonable.
JS
--000e0cd487cc2a5a9904acd4a720
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Fixing (2) is easier; incorporating a ntp library and/or simply<br>
removing the bitcoin mining code from the client but requiring pools<br>
and miners to have accurate-to-within-a-minute system clocks (or their<br>
blocks will be "discouraged") seems reasonable to me. </blockquot=
e><div>=A0<br>Incorporating NTP seems overkill. Most OSes come with NTP sup=
port integrated these days (even XP did?), there is no excuse to not be run=
ning it, especially on a server.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.=
8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">If you =
want to<br>
produce blocks that the rest of the network will accept, run ntp on<br>
your system.<br></blockquote><div><br>Requiring it for miners sounds very r=
easonable.<br><br>JS<br><br></div></div>
--000e0cd487cc2a5a9904acd4a720--
|
