<oembed><type>rich</type><version>1.0</version><author_name>npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n</author_name><author_url>https://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2016-03-02&#xA;📝 Original message:On Wednesday, March 02, 2016 3:05:08 PM Pavel Janík wrote:&#xA;&gt; &gt; the network. This would result in a significantly longer block interval,&#xA;&gt; &gt; which also means a higher per-block transaction volume, which could&#xA;&gt; &gt; cause the block size limit to legitimately be hit much sooner than&#xA;&gt; &gt; expected.&#xA;&gt; &#xA;&gt; If this happens at all (the exchange rate of the coin can accomodate such&#xA;&gt; expectation),&#xA;&#xA;The exchange rate is not significantly influenced by these things. &#xA;Historically, it seems fairly obvious that the difficulty has followed value, &#xA;not value following difficulty.&#xA;&#xA;&gt; the local fee market will develop, fees will raise and complement mined&#xA;&gt; coins, thus bringing more miners back to the game (together with expected&#xA;&gt; higher exchange rate).&#xA;&#xA;Depends on the hashrate drop, and tolerance for higher fees, both of which are &#xA;largely unknown at this time. At least having code prepared for the negative &#xA;scenarios in case of an emergency seems reasonable, even if we don&#39;t end up &#xA;needing to deploy it.&#xA;&#xA;Luke</html></oembed>