📅 Original date posted:2017-02-05
📝 Original message: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
Andrew C [ARCHIVE] /
npub1vc…xz0wk
2023-06-07 17:56:01
in reply to nevent1q…ejca
Author Public Key
npub1vceyhqxfhemlfq82ztdv9gqgc08zq2680yzy4dfuly7h8pqrkwps0xz0wkPublished at
2023-06-07 17:56:01Event JSON
{
"id": "01e3766fd85e6a83d0fe502def464b0b6da951aae799fb3f751487d074734e44",
"pubkey": "66324b80c9be77f480ea12dac2a008c3ce202b4779044ab53cf93d738403b383",
"created_at": 1686160561,
"kind": 1,
"tags": [
[
"e",
"6eddf1a13d41cd54af30531855ceb7d14eb31ca00a80520a5a643c560fb7dfbd",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2017-02-05\n📝 Original message:Hello all,\n\nMany people have expressed discontent with Luke-jr's proposed block size\nBIP, in particular with the decrease in size that would occur if it were\nto be activated prior to 2024.\n\nI have decided to modify the proposal to instead begin the increase\nsteps at the current 1000000 byte limit. The increases and the time spam\nof each increase will remain the same, just that the increase begins\nfrom 1000000 bytes instead of 300000 bytes.\n\nFurthermore, instead of a fixed schedule from a fixed point in time, the\nincreases will instead be calculated off of the MTP of the activation\nblock (the first block to be in the active state for this fork).\n\nWhile this proposal shares many of the same issues with the one it\nmodifies, I hope that it will be slightly less controversial and can\nallow us to move forward with scaling Bitcoin.\n\nThe full text of the proposal can be found at\nhttps://github.com/achow101/bips/blob/bip-blksize/bip-blksize.mediawiki.\nMy implementation of it is available at\nhttps://github.com/achow101/bitcoin/tree/bip-blksize\n\n\nAndrew",
"sig": "e7ed76e0425ecad546df7cb75cc9f206e2408ac6ddbc8e3f61b41abffe7510632a30281f6ab2a76ba2403e27fddbf311952236cb97ca392d6896733a537212f9"
}