📅 Original date posted:2015-08-18
📝 Original message:-> You need to take into account the reward halving, likely to be in
3Q2016. Forks and reward halving at the same time would possibly be a bad
combination.
-> The original proposed date for the fork was December 2015. It was pushed
back to January as December is a busy period for a lot of people and
businesses. Likewise, June is a busy period for people. July / August is a
good period as it is quiet because people go on holiday. A window of 2
months during holiday periods is better than starting in June. January 2016
is better, mainly because of the excessive reward halving chatter likely to
be going on..
..
> Proposal (parameters in ** are my recommendations but negotiable):
>
> 1. Today, we all agree that some kind of block size hardfork will happen
> on t1=*1 June 2016*
>
> 2. If no other consensus could be reached before t2=*1 Feb 2016*, we will
> adopt the backup plan
>
> 3. The backup plan is: t3=*30 days* after m=*80%* of miner approval, but
> not before t1=*1 June 2016*, the block size is increased to s=*1.5MB*
>
> 4. If the backup plan is adopted, we all agree that a better solution
> should be found before t4=*31 Dec 2017*.
> ..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150818/eff641b4/attachment.html>;
Ahmed Zsales [ARCHIVE] /
npub105…lgz5a
2023-06-07 15:48:17
in reply to nevent1q…u6r3
Author Public Key
npub105eg2ny7gs448umtlsn4ns4slc5q3se8wpnzhtr22j8sgdrv2q7stlgz5aPublished at
2023-06-07 15:48:17Event JSON
{
"id": "c5c34fb6ca9a362e1068495a7d2232195799988669fad64511d865e5221275c8",
"pubkey": "7d32854c9e442b53f36bfc2759c2b0fe2808c32770662bac6a548f04346c503d",
"created_at": 1686152897,
"kind": 1,
"tags": [
[
"e",
"d1741ba43ee3659ec018c6d08510dcfe36f706cba8efd0c9670cfaa6540ca5b4",
"",
"root"
],
[
"e",
"3768c181d1e242a5872b6341f4aa4deaf2d0ea5896d4d6b36ae0eb0a51cad8c3",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2015-08-18\n📝 Original message:-\u003e You need to take into account the reward halving, likely to be in\n3Q2016. Forks and reward halving at the same time would possibly be a bad\ncombination.\n\n-\u003e The original proposed date for the fork was December 2015. It was pushed\nback to January as December is a busy period for a lot of people and\nbusinesses. Likewise, June is a busy period for people. July / August is a\ngood period as it is quiet because people go on holiday. A window of 2\nmonths during holiday periods is better than starting in June. January 2016\nis better, mainly because of the excessive reward halving chatter likely to\nbe going on..\n\n..\n\u003e Proposal (parameters in ** are my recommendations but negotiable):\n\u003e\n\u003e 1. Today, we all agree that some kind of block size hardfork will happen\n\u003e on t1=*1 June 2016*\n\u003e\n\u003e 2. If no other consensus could be reached before t2=*1 Feb 2016*, we will\n\u003e adopt the backup plan\n\u003e\n\u003e 3. The backup plan is: t3=*30 days* after m=*80%* of miner approval, but\n\u003e not before t1=*1 June 2016*, the block size is increased to s=*1.5MB*\n\u003e\n\u003e 4. If the backup plan is adopted, we all agree that a better solution\n\u003e should be found before t4=*31 Dec 2017*.\n\u003e ..\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150818/eff641b4/attachment.html\u003e",
"sig": "b53d3f7526e53ac5547fcdad6807afea55ea680e846843c9ff3fce4047c229160682ee4c968b66a0ae6d8eb2ee48211db255bfeb19c12f3656ed6e0d6c61603b"
}