<oembed><type>rich</type><version>1.0</version><author_name>npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_name><author_url>https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-23&#xA;📝 Original message:On Tue, Jun 23, 2015 at 04:12:17PM -0400, Gavin Andresen wrote:&#xA;&gt; &gt; In particular, if bandwidth scaling doesn&#39;t go according to your plan,&#xA;&gt; &gt; e.g. the exponential exponent is too large, perhaps due to technological&#xA;&gt; &gt; growth not keeping pace, or the political realities of actual bandwidth&#xA;&gt; &gt; deployment making theoretical technological growth irrelevant, what&#xA;&gt; &gt; mechanism will prevent centralization? (if any)&#xA;&gt; &#xA;&gt; &#xA;&gt; Simulations show that:&#xA;&gt; &#xA;&gt; Latency/bandwidth matter for miners.  Low latency, high bandwidth is&#xA;&gt; better. However, miners with bad connectivity can simply create smaller&#xA;&gt; blocks...&#xA;&#xA;Pieter Wuille showed with simulations that miners with bad connectivity&#xA;are negatively affected by other miners creating larger blocks.&#xA;Similarly I showed that with equation-based analysis. I&#39;ve seen no&#xA;response to either argument, and it&#39;s a centralization pressure.&#xA;&#xA;Note how propagation times are important enough to miners that they&#xA;already mine on top of unverified headers from other miners to increase&#xA;profitability, a grave threat to the security of the Bitcoin network.&#xA;&#xA;&gt; ... until transaction fees become significant.  But by the time that&#xA;&gt; happens, protocol optimizations of block propagation will make the block&#xA;&gt; size an insignificant term in the &#34;how profitable is it to mine in THIS&#xA;&gt; particular place on the Internet / part of the world&#34; equation.&#xA;&#xA;These block propagation improvements are both already implemented (Matt&#xA;Corallo&#39;s relay network, p2pool) and require co-operation.&#xA;&#xA;For instance, notice the recent full-RBF debate where Coinbase said&#xA;they&#39;d consider getting contracts directly with miners to get&#xA;transactions they desired mined even when they otherwise would not be&#xA;due to double-spends. This is one of many scenarios where block&#xA;propagation improvements fail. Thus for a safety engineering&#xA;analysis we need to talk about worst-case scenarios.&#xA;&#xA;Equally, I don&#39;t see any analysis from anyone of that % of non-optimized&#xA;transactions need to fail for what kind of centralizing pressure.&#xA;&#xA;&#xA;In any case, this ponts to the need for your proposal to explictly talk&#xA;about what kind of resources are needed by miners for what kind of&#xA;profitability, including the case where other miners are sabotaging&#xA;their profitability.&#xA;&#xA;-- &#xA;&#39;peter&#39;[:-1]@petertodd.org&#xA;000000000000000008c0be16e152f86ab3a271a13c3f41c56228d72990abf7bd&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: signature.asc&#xA;Type: application/pgp-signature&#xA;Size: 650 bytes&#xA;Desc: Digital signature&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150623/97ccb0af/attachment.sig&gt;</html></oembed>