<oembed><type>rich</type><version>1.0</version><author_name>npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw</author_name><author_url>https://nostr.ae/npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-05-28&#xA;📝 Original message:On Thu, May 28, 2015 at 1:05 PM, Mike Hearn &lt;mike at plan99.net&gt; wrote:&#xA;&#xA;&gt; Isn&#39;t that a step backwards, then? I see no reason for fee pressure to&#xA;&gt;&gt; exist at the moment. All it&#39;s doing is turning away users for no purpose:&#xA;&gt;&gt; mining isn&#39;t supported by fees, and the tiny fees we use right now seem to&#xA;&gt;&gt; be good enough to stop penny flooding.&#xA;&gt;&gt;&#xA;&gt;&#xA;&gt; Why not set the max size to be 20x the average size? Why 2x, given you&#xA;&gt; just pointed out that&#39;d result in blocks shrinking rather than growing.&#xA;&gt;&#xA;&#xA;Twenty is scary.&#xA;&#xA;And two is a very neutral number: if 50% of hashpower want the max size to&#xA;grow as fast as possible and 50% are dead-set opposed to any increase in&#xA;max size, then half produce blocks 2 times as big, half produce empty&#xA;blocks, and the max size doesn&#39;t change. If it was 20, then a small&#xA;minority of miners could force a max size increase.  (if it is less than 2,&#xA;then a minority of minors can force the block size down)&#xA;&#xA;&#xA;As for whether there &#34;should&#34; be fee pressure now or not: I have no&#xA;opinion, besides &#34;we should make block propagation faster so there is no&#xA;technical reason for miners to produce tiny blocks.&#34; I don&#39;t think us&#xA;developers should be deciding things like whether or not fees are too high,&#xA;too low, .....&#xA;&#xA;-- &#xA;--&#xA;Gavin Andresen&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150528/ef414a76/attachment.html&gt;</html></oembed>