<oembed><type>rich</type><version>1.0</version><author_name>Vladimir Marchenko [ARCHIVE] (npub1ya…f362l)</author_name><author_url>https://nostr.ae/npub1yad6fmp7zh9rc0lpzecu5dtgy2yye4f7mvf3wdn8rulxntcx0czswf362l</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: Bitcoin&#39;s code for time synchronization is a hack, but fixing it by incorporating an ntp library or removing mining code seems reasonable to experts.&#xA;📝 Original message:&gt; 2) Bitcoin&#39;s &#34;what time is it&#34; code is kind of a hack.&#xA;...&#xA;&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. If you want to&#xA;&gt; produce blocks that the rest of the network will accept, run ntp on&#xA;&gt; your system.&#xA;...&#xA;&gt; --&#xA;&gt; Gavin Andresen&#xA;&gt;&#xA;&#xA;As a miner I fully support route (2) and do not think that this would&#xA;cause any serious issues or discontent among miners. Most miners&#xA;surely are running ntpd already. Those who mess with the clock&#xA;intentionally will have to play ball.&#xA;&#xA;--&#xA;Vladimir&#xA;-&#xA;http://bitcoin.org.uk/forums - clean and moderated bitcoin forum</html></oembed>