From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: References: Date: Tue, 13 Sep 2011 15:54:04 +0000 Message-ID: From: John Smith To: Gavin Andresen 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
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.
=A0
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.

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 r= easonable.

JS

--000e0cd487cc2a5a9904acd4a720--