<oembed><type>rich</type><version>1.0</version><author_name>npub1jdl3plz00rvxwc6g2ckemzrgg0amx5wen4kfvs3laxtssxvk9cvsf3gh0m</author_name><author_url>https://nostr.ae/npub1jdl3plz00rvxwc6g2ckemzrgg0amx5wen4kfvs3laxtssxvk9cvsf3gh0m</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-07-30&#xA;📝 Original message:What, if any, methods would be used for miners to communicate their&#xA;upgrade?&#xA;&#xA;Greg&#xA;&#xA;On Thu, Jul 30, 2015 at 10:25 AM, Pieter Wuille via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt; Hello all,&#xA;&gt;&#xA;&gt; here is a proposal for long-term scalability I&#39;ve been working on:&#xA;&gt; https://gist.github.com/sipa/c65665fc360ca7a176a6&#xA;&gt;&#xA;&gt; Some things are not included yet, such as a testnet whose size runs ahead&#xA;&gt; of the main chain, and the inclusion of Gavin&#39;s more accurate sigop&#xA;&gt; checking after the hard fork.&#xA;&gt;&#xA;&gt; Comments?&#xA;&gt;&#xA;&gt; --&#xA;&gt; Pieter&#xA;&gt;&#xA;&gt;&#xA;&gt; _______________________________________________&#xA;&gt; bitcoin-dev mailing list&#xA;&gt; bitcoin-dev at lists.linuxfoundation.org&#xA;&gt; https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev&#xA;&gt;&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150730/846a30c7/attachment-0001.html&gt;</html></oembed>