<oembed><type>rich</type><version>1.0</version><author_name>npub1fvuxqdqg7klqqgy3yy8gdxjv4phu92sll5y8zqm2qe5qdrhxymhqf3vq7f</author_name><author_url>https://nostr.ae/npub1fvuxqdqg7klqqgy3yy8gdxjv4phu92sll5y8zqm2qe5qdrhxymhqf3vq7f</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-05-09&#xA;📝 Original message:&gt;&#xA;&gt;&#xA;&gt;&#xA;&gt; You suggested &#34;If the maximum block weight is set to 2.7M, each byte of&#xA;&gt; non-witness block costs 1.7&#34;, but these numbers dont work out - setting&#xA;&gt; the discount to 1.7 gets you a maximum block size of 1.7MB (in a soft&#xA;&gt; fork), not 2.7MB.&#xA;&#xA;&#xA;Yes. In a soft-fork is true.&#xA;I was thinking about what a HF could do to optimize the balance, and I&#xA;forgot I was in the context of a SF.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170509/473e88df/attachment.html&gt;</html></oembed>