{"type":"rich","version":"1.0","author_name":"npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jafl","author_url":"https://nostr.ae/npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jafl","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-09-13\n🗒️ Summary of this message: Incorporating NTP or removing bitcoin mining code from the client but requiring accurate system clocks for miners seems reasonable.\n📝 Original message:\u003e Fixing (2) is easier; incorporating a ntp library and/or simply\n\u003e removing the bitcoin mining code from the client but requiring pools\n\u003e and miners to have accurate-to-within-a-minute system clocks (or their\n\u003e blocks will be \"discouraged\") seems reasonable to me.\n\n\nIncorporating NTP seems overkill. Most OSes come with NTP support integrated\nthese days (even XP did?), there is no excuse to not be running it,\nespecially on a server.\n\nIf you want to\n\u003e produce blocks that the rest of the network will accept, run ntp on\n\u003e your system.\n\u003e\n\nRequiring it for miners sounds very reasonable.\n\nJS\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110913/1fa29c73/attachment.html\u003e"}