<oembed><type>rich</type><version>1.0</version><author_name>npub1vceyhqxfhemlfq82ztdv9gqgc08zq2680yzy4dfuly7h8pqrkwps0xz0wk</author_name><author_url>https://nostr.ae/npub1vceyhqxfhemlfq82ztdv9gqgc08zq2680yzy4dfuly7h8pqrkwps0xz0wk</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-02-05&#xA;📝 Original message:Hello all,&#xA;&#xA;Many people have expressed discontent with Luke-jr&#39;s proposed block size&#xA;BIP, in particular with the decrease in size that would occur if it were&#xA;to be activated prior to 2024.&#xA;&#xA;I have decided to modify the proposal to instead begin the increase&#xA;steps at the current 1000000 byte limit. The increases and the time spam&#xA;of each increase will remain the same, just that the increase begins&#xA;from 1000000 bytes instead of 300000 bytes.&#xA;&#xA;Furthermore, instead of a fixed schedule from a fixed point in time, the&#xA;increases will instead be calculated off of the MTP of the activation&#xA;block (the first block to be in the active state for this fork).&#xA;&#xA;While this proposal shares many of the same issues with the one it&#xA;modifies, I hope that it will be slightly less controversial and can&#xA;allow us to move forward with scaling Bitcoin.&#xA;&#xA;The full text of the proposal can be found at&#xA;https://github.com/achow101/bips/blob/bip-blksize/bip-blksize.mediawiki.&#xA;My implementation of it is available at&#xA;https://github.com/achow101/bitcoin/tree/bip-blksize&#xA;&#xA;&#xA;Andrew</html></oembed>