<oembed><type>rich</type><version>1.0</version><author_name>npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jafl</author_name><author_url>https://nostr.ae/npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jafl</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2011-09-13&#xA;🗒️ Summary of this message: Incorporating NTP or removing bitcoin mining code from the client but requiring accurate system clocks for miners seems reasonable.&#xA;📝 Original message:&gt; Fixing (2) is easier; incorporating a ntp library and/or simply&#xA;&gt; removing the bitcoin mining code from the client but requiring pools&#xA;&gt; and miners to have accurate-to-within-a-minute system clocks (or their&#xA;&gt; blocks will be &#34;discouraged&#34;) seems reasonable to me.&#xA;&#xA;&#xA;Incorporating NTP seems overkill. Most OSes come with NTP support integrated&#xA;these days (even XP did?), there is no excuse to not be running it,&#xA;especially on a server.&#xA;&#xA;If you want to&#xA;&gt; produce blocks that the rest of the network will accept, run ntp on&#xA;&gt; your system.&#xA;&gt;&#xA;&#xA;Requiring it for miners sounds very reasonable.&#xA;&#xA;JS&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110913/1fa29c73/attachment.html&gt;</html></oembed>