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