📅 Original date posted:2017-02-05
📝 Original message:My BIP draft didn't make progress because the community opposes any block size
increase hardfork ever. Your version doesn't address the current block size
issues (ie, the blocks being too large). So you've retained the only certain-
DOA parts of my proposal, and removed the most useful part... I'm not sure the
point. Also, your version is now EXCLUSIVELY a hardfork, so it makes no sense
to keep the BIP 9 deployment at all - either it gets consensus or it doesn't,
but miners have no part in deployment of it.
On Sunday, February 05, 2017 9:50:26 PM Andrew C via bitcoin-dev wrote:
> Hello all,
>
> Many people have expressed discontent with Luke-jr's proposed block size
> BIP, in particular with the decrease in size that would occur if it were
> to be activated prior to 2024.
>
> I have decided to modify the proposal to instead begin the increase
> steps at the current 1000000 byte limit. The increases and the time spam
> of each increase will remain the same, just that the increase begins
> from 1000000 bytes instead of 300000 bytes.
>
> Furthermore, instead of a fixed schedule from a fixed point in time, the
> increases will instead be calculated off of the MTP of the activation
> block (the first block to be in the active state for this fork).
>
> While this proposal shares many of the same issues with the one it
> modifies, I hope that it will be slightly less controversial and can
> allow us to move forward with scaling Bitcoin.
>
> The full text of the proposal can be found at
> https://github.com/achow101/bips/blob/bip-blksize/bip-blksize.mediawiki.
> My implementation of it is available at
> https://github.com/achow101/bitcoin/tree/bip-blksize
>
>
> Andrew
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 17:56:02
in reply to nevent1q…9hsy
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 17:56:02Event JSON
{
"id": "b667745a5fbb2bb146fd883ecea822817ec7879b98e2e35342c67e0ac96ba132",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686160562,
"kind": 1,
"tags": [
[
"e",
"6eddf1a13d41cd54af30531855ceb7d14eb31ca00a80520a5a643c560fb7dfbd",
"",
"root"
],
[
"e",
"01e3766fd85e6a83d0fe502def464b0b6da951aae799fb3f751487d074734e44",
"",
"reply"
],
[
"p",
"66324b80c9be77f480ea12dac2a008c3ce202b4779044ab53cf93d738403b383"
]
],
"content": "📅 Original date posted:2017-02-05\n📝 Original message:My BIP draft didn't make progress because the community opposes any block size \nincrease hardfork ever. Your version doesn't address the current block size \nissues (ie, the blocks being too large). So you've retained the only certain-\nDOA parts of my proposal, and removed the most useful part... I'm not sure the \npoint. Also, your version is now EXCLUSIVELY a hardfork, so it makes no sense \nto keep the BIP 9 deployment at all - either it gets consensus or it doesn't, \nbut miners have no part in deployment of it.\n\nOn Sunday, February 05, 2017 9:50:26 PM Andrew C via bitcoin-dev wrote:\n\u003e Hello all,\n\u003e \n\u003e Many people have expressed discontent with Luke-jr's proposed block size\n\u003e BIP, in particular with the decrease in size that would occur if it were\n\u003e to be activated prior to 2024.\n\u003e \n\u003e I have decided to modify the proposal to instead begin the increase\n\u003e steps at the current 1000000 byte limit. The increases and the time spam\n\u003e of each increase will remain the same, just that the increase begins\n\u003e from 1000000 bytes instead of 300000 bytes.\n\u003e \n\u003e Furthermore, instead of a fixed schedule from a fixed point in time, the\n\u003e increases will instead be calculated off of the MTP of the activation\n\u003e block (the first block to be in the active state for this fork).\n\u003e \n\u003e While this proposal shares many of the same issues with the one it\n\u003e modifies, I hope that it will be slightly less controversial and can\n\u003e allow us to move forward with scaling Bitcoin.\n\u003e \n\u003e The full text of the proposal can be found at\n\u003e https://github.com/achow101/bips/blob/bip-blksize/bip-blksize.mediawiki.\n\u003e My implementation of it is available at\n\u003e https://github.com/achow101/bitcoin/tree/bip-blksize\n\u003e \n\u003e \n\u003e Andrew\n\u003e \n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev",
"sig": "09d9bfcf8bf42c389e1fd9cc3363771ee118715d0cc7a23ba2d327f994df62c5eda09583ca3fa0f66365a8e5279b1bf10041456854dc366d98319e82d4d2c4f6"
}