<oembed><type>rich</type><version>1.0</version><author_name>npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_name><author_url>https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2012-09-10&#xA;📝 Original message:On Mon, Sep 10, 2012 at 3:53 PM, Matt Corallo &lt;bitcoin-list at bluematt.me&gt; wrote:&#xA;&gt; It seems to me the whole idea of segmenting blocks would add very little&#xA;&gt; (to nothing) with any sane block size.  Sure, if a block were to be&#xA;&gt; 10GB, it may make sense.  However, even in that case, it would be easier&#xA;&#xA;As you know there is a hard protocol limit of 1MB.&#xA;&#xA;If you&#39;re going to talk about doing that you are screwing with the&#xA;core economic promises of the system. (in particular, removing the cap&#xA;eliminates the only armwave we have for long term security).  But in&#xA;any case, removing it requires a complete and totally incompatible&#xA;hardfork, and at that point you can do whatever you want with the&#xA;protocol. Changing how blocks are fetched is almost incidental to the&#xA;number of other things that would be changed.  I don&#39;t think it makes&#xA;sense to design for that especially when something far simpler (as you&#xA;pointed out) is prudent for the design of bitcoin.</html></oembed>