<oembed><type>rich</type><version>1.0</version><author_name>npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_name><author_url>https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-08-05&#xA;📝 Original message:On Wed, Aug 5, 2015 at 9:29 AM, Elliot Olds &lt;elliot.olds at gmail.com&gt; wrote:&#xA;&gt; On Tue, Aug 4, 2015 at 4:59 AM, Jorge Timón&#xA;&gt; &lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt;&gt;&#xA;&gt;&gt; Also I don&#39;t think &#34;hitting the limit&#34; must be necessarily harmful and&#xA;&gt;&gt; if it is, I don&#39;t understand why hitting it at 1MB will be more&#xA;&gt;&gt; harmful than hitting it at 2MB, 8MB or 8GB.&#xA;&gt;&#xA;&gt;&#xA;&gt; I don&#39;t think merely hitting the limit is bad. The level of tx fees in&#xA;&gt; equilibrium give some clue as to the level of harm being done. If fees are&#xA;&gt; at $5/tx at 1MB, it&#39;s about as bad as if fees are at $5/tx at 4MB.&#xA;&#xA;This is a much more reasonable position. I wish this had been starting&#xA;point of this discussion instead of &#34;the block size limit must be&#xA;increased as soon as possible or bitcoin will fail&#34;.&#xA;If the only fear about not increasing the block size fast enough is&#xA;that fees may rise, pieter wouldn&#39;t had to repeatedly explain that for&#xA;any reasonable block size some use case may fill the blocks rapidly.&#xA;&#xA;&gt;&gt; There is NO criterion based on mining centralization to decide between&#xA;&gt;&gt; 2 sizes in favor of the small one.&#xA;&gt;&gt; It seems like the rationale it&#39;s always &#34;the bigger the better&#34; and&#xA;&gt;&gt; the only limitation is what a few people concerned with mining&#xA;&gt;&gt; centralization (while they still have time to discuss this) are&#xA;&gt;&gt; willing to accept. If that&#39;s the case, then there won&#39;t be effectively&#xA;&gt;&gt; any limit in the long term and Bitcoin will probably fail in its&#xA;&gt;&gt; decentralization goals.&#xA;&gt;&gt; I think its the proponents of a blocksize change who should propose&#xA;&gt;&gt; such a criterion and now they have the tools to simulate different&#xA;&gt;&gt; block sizes.&#xA;&gt;&#xA;&gt;&#xA;&gt; In the absence of harder data, it might be interesting to use these&#xA;&gt; simulations to graph centralization pressure as a function of bandwidth cost&#xA;&gt; over time (or other historical variables that affect centralization). For&#xA;&gt; instance, look at how high centralization pressure was in 2009 according to&#xA;&gt; the simulations, given how cheap/available bandwidth was then, compared to&#xA;&gt; 2010, 2011, etc. Then we could figure out: given today&#39;s bandwidth&#xA;&gt; situation, what size blocks right now would give us the same centralization&#xA;&gt; pressure that we had in 2011, 2012, 2013, etc?&#xA;&gt;&#xA;&gt; Of course this doesn&#39;t mean we should blindly assume that the level of&#xA;&gt; centralization pressure in 2012 was acceptable, and therefore any block size&#xA;&gt; increase that results in the same amount of pressure now should be&#xA;&gt; acceptable. But it might lead to a more productive discussion.&#xA;&#xA;This sounds good overall but I&#39;m afraid you are oversimplifying some things.&#xA;Centralization pressure not only comes from global average bandwidth&#xA;costs and block propagation times is not the only concern.&#xA;Here&#39;s an extreme example: [1]&#xA;But anyway, yes, I agree, ANY metric would be better than nothing (the&#xA;current situation).&#xA;&#xA;&gt;&gt; I want us to simulate many blocksizes before rushing into a decision&#xA;&gt;&gt; (specially because I disagree that taking a decision there is urgent&#xA;&gt;&gt; in the first place).&#xA;&gt;&#xA;&gt;&#xA;&gt; IMO it is not urgent if the core devs are committed to reacting to a huge&#xA;&gt; spike in tx fees with a modest block size increase in a relatively short&#xA;&gt; time frame, if they judge the centralization risks of that increase to be&#xA;&gt; small. Greg Maxwell posted on reddit a while back something to the effect of&#xA;&gt; &#34;the big block advocates are overstating the urgency of the block size&#xA;&gt; increase, because if there was actually a situation that required us to&#xA;&gt; increase block size, we could make the increase when it was actually&#xA;&gt; needed.&#34; I found that somewhat persuasive, but I am concerned that I haven&#39;t&#xA;&gt; seen any discussion of what the &#34;let&#39;s wait for now&#34; camp would consider a&#xA;&gt; valid reason to increase block size in the short term, and how they&#39;d make&#xA;&gt; the tradeoff with tx fees or whatever else was necessitating the increase.&#xA;&#xA;Given that for any non-absurdly-big size some transactions will&#xA;eventually be priced out, and that the consensus rule serves for&#xA;limiting mining centralization (and more indirectly centralization in&#xA;general) and not about trying to set a given average transaction fee,&#xA;I think the current level of mining centralization will always be more&#xA;relevant than the current fee level when discussing any change to the&#xA;consensus rule to limit centralization (at any point in time).&#xA;In other words, the question &#34;can we change this without important&#xA;risks of destroying the decentralized properties of the system in the&#xA;short or long run?&#34; should be always more important than &#34;is there a&#xA;concerning rise in fees to motivate this change at all?&#34;.&#xA;&#xA;&gt; Jorge, if a fee equilibrium developed at 1MB of $5/tx, and you somehow knew&#xA;&gt; with certainty that increasing to 4MB would result in a 20 cent/tx&#xA;&gt; equilibrium that would last for a year (otherwise fees would stay around $5&#xA;&gt; for that year), would you be in favor of an increase to 4MB?&#xA;&#xA;As said, I would always consider the centralization risks first: I&#39;d&#xA;rather have a $5/tx decentralized Bitcoin than a Bitcoin with free&#xA;transactions but effectively validated (when they validate blocks they&#xA;mine on top of) by around 10 miners, specially if only 3 of them could&#xA;easily collude to censor transactions [orphaning any block that&#xA;doesn&#39;t censor in the same manner]. Sadly I have no choice, the later&#xA;is what we have right now. And reducing the block size can&#39;t guarantee&#xA;that the situation will get better or even that fees could rise to&#xA;$5/tx (we just don&#39;t have that demand, not that it is a goal for&#xA;anyone). All I know is that increasing the block size *could*&#xA;(conditional, not necessarily, I don&#39;t know in which cases, I don&#39;t&#xA;think anybody does) make things even worse.&#xA;&#xA;On the other hand, I could understand people getting worried if fees&#xA;where as high as $5/tx or even 20 cent/tx but we&#39;re very far away from&#xA;that case. How can low subsidies (a certainty) be &#34;too far in the&#xA;future to worry about it&#34; but $5/tx, 20 cent/tx or even 5 cent/tx an&#xA;urgent concern? For all I know, 5 cent/tx may not happen in the next&#xA;25 years: it may never happen. And if it happens, to me it will be a&#xA;symptom of Bitcoin success, even for others it means that Bitcoin has&#xA;become a &#34;high value settlement network&#34;.&#xA;To the question&#xA;&#xA;- At which minimum mining fee rate will you urge others to change the&#xA;consensus rules to increase the block size?&#xA;&#xA;I&#39;m very sorry, but my answer is:&#xA;&#xA;- I honestly don&#39;t know, that may never happen.&#xA;&#xA;What I can tell you is this: I will never be worried about &#34;too high&#xA;fees&#34; while the fees remain at 0 (null, zero, nothing, cero, nada,&#xA;zilch).&#xA;That&#39;s right, no matter what wallet&#39;s defaults chose for their users,&#xA;no matter what the minimum relay fee policy does to the &#34;fee market&#34;&#xA;and how much urgent transactions pay in fees; the fact remains that in&#xA;practice non-urgent transactions usually (when the raw transaction&#39;s&#xA;structure it&#39;s appropriate) don&#39;t have to pay fees.&#xA;&#xA;I&#39;m still missing an answer from the &#34;big blocks size side&#34; to the&#xA;following question (which I have insistently repeated with various&#xA;permutations):&#xA;&#xA;If &#34;not now&#34; when will it be a good time to let fees rise above zero?&#xA;After the next subsidy halving? After 4 more subsidy halvings (ie&#xA;about 13 years from now, subsidy = 1.5625 btc/block )? After your&#xA;grandmother abandons her national currency and uses Bitcoin for&#xA;everything? Never?&#xA;&#xA;ANY answer (maybe with the exception of the last one) would be less&#xA;worrying than silence.&#xA;&#xA;&gt; For those familiar with the distinction between near/far mode thinking&#xA;&gt; popularized by Robin Hanson: focusing on concrete examples like this&#xA;&gt; encourages problem solving and consensus, and focusing on abstract&#xA;&gt; principles (like decentralization vs. usability in general) leads to people&#xA;&gt; toward using argument to signal their alliances and reduce the status of&#xA;&gt; their opponents.&#xA;&#xA;I really appreciate your efforts to mediate in this dispute and I&#xA;honestly hope that my previous answer is useful as it is.&#xA;&#xA;&gt; I think it&#39;d be very helpful if more 1MB advocates&#xA;&gt; described what exactly would make them say &#34;OK, in this situation a block&#xA;&gt; size increase is needed, we should do one quickly!&#34;, and also if&#xA;&gt; Gavin/Mike/Jeff described what hypothetical scenarios and/or test results&#xA;&gt; would make them want to stick with 1MB blocks for now.&#xA;&#xA;Just replace 1MB with ANY size.&#xA;But, yes, please, when will you consider a size to be too dangerous&#xA;for centralization?&#xA;Why 20 GB would have been safe but 21 GB wouldn&#39;t have been (or the&#xA;respective maximums and respective +1)?&#xA;&#xA;Note that &#34;Never, 20GB was just a number closer to infinity than 1MB&#xA;and I hoped that could had been voluntarily accepted by users. What I&#xA;really want is to completely remove this consensus rule forever.&#34; is a&#xA;perfectly valid answer. It just means that I will agree with people&#xA;that think this way as explained in [1] (yes, not even after&#xA;superluminal communication).&#xA;&#xA;As an less relevant note, I feel extremely uncomfortable about being&#xA;included in the &#34;1MB advocates&#34; group. As I&#39;ve tried to explain&#xA;several times, 1 is to me an arbitrary number like any other (at most,&#xA;the canonical arbitrary number), and so it is 1000000&#xA;(MAX_BLOCK_SIZE). I rarely like being grouped or labelled, but maybe&#xA;something more accurate like &#34;not-recklessly-change-consensus-rules&#xA;advocates&#34; would help.&#xA;There&#39;s nothing special about 1MB apart from being the current rule,&#xA;so I don&#39;t think the number is that much relevant to the discussion.&#xA;Grouping anyone that has raised any concern about rising the consensus&#xA;block size limit as &#34;the 1MBers&#34; is about as fair as grouping anyone&#xA;that has ever proposed a rise in the maximum size as &#34;the 20GBers&#34;&#xA;(specially when there&#39;s people that belong to both groups&#xA;simultaneously, like Pieter Wuille who started this thread, and whose&#xA;proposal we&#39;re supposed to be discussing).&#xA;&#xA;[1] http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/009947.html</html></oembed>