<oembed><type>rich</type><version>1.0</version><author_name>npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd</author_name><author_url>https://nostr.ae/npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-05-06&#xA;📝 Original message:On Thu, May 7, 2015 at 12:12 AM, Matt Corallo &lt;bitcoin-list at bluematt.me&gt;&#xA;wrote:&#xA;&#xA;&gt; The point of the hard block size limit is exactly because giving miners&#xA;&gt; free rule to do anything they like with their blocks would allow them to&#xA;&gt; do any number of crazy attacks. The incentives for miners to pick block&#xA;&gt; sizes are no where near compatible with what allows the network to&#xA;&gt; continue to run in a decentralized manner.&#xA;&gt;&#xA;&#xA;Miners can always reduce the block size (if they coordinate).  Increasing&#xA;the maximum block size doesn&#39;t necessarily cause an increase.  A majority&#xA;of miners can soft-fork to set the limit lower than the hard limit.&#xA;&#xA;Setting the hard-fork limit higher means that a soft fork can be used to&#xA;adjust the limit in the future.&#xA;&#xA;The reference client would accept blocks above the soft limit for wallet&#xA;purposes, but not build on them.  Blocks above the hard limit would be&#xA;rejected completely.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150507/b5a9be4e/attachment.html&gt;</html></oembed>