<oembed><type>rich</type><version>1.0</version><author_name>npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw</author_name><author_url>https://nostr.ae/npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-22&#xA;📝 Original message:On Mon, Jun 22, 2015 at 4:46 PM, Gavin Andresen &lt;gavinandresen at gmail.com&gt;&#xA;wrote:&#xA;&#xA;&gt; Excellent point. That could only happen if activation happened on 11 Jan&#xA;&gt; 2016; instead of complicating the code and spec with another condition, I&#xA;&gt; think it would be better to specify that the activation date is the later&#xA;&gt; of the miner supermajority and 11 Jan, with the first big block two weeks&#xA;&gt; later.&#xA;&gt;&#xA;&#xA;.... I take that back, I&#39;m wrong and Tier is correct: if activation&#xA;happened right at midnight 11 Jan 2016 and the next block&#39;s timestamp was&#xA;before midnight, that next block would just be limited to 1MB in size.&#xA;&#xA;-- &#xA;--&#xA;Gavin Andresen&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150622/385adf94/attachment.html&gt;</html></oembed>