<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 3/26/2017 1:22 PM, Bryan Bishop via bitcoin-dev wrote:<br>
    <blockquote
cite="mid:CABaSBayb-FAt0XOX9u+T3-Z2gJQAV-Y7xZS_k6YG74VhPqejQA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Sun, Mar 26, 2017 at 2:05 PM,
            Peter R via bitcoin-dev <span dir="ltr">&lt;<a
                moz-do-not-send="true"
                href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                target="_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div style="word-wrap:break-word">
                <div>
                  <div>
                    <div>With a tightening of the rule set, a hash power
                      minority that has not upgraded will not produce a
                      minority branch; instead they will simply have any
                      invalid blocks they produce orphaned, serving as a
                      wake-up call to upgrade.</div>
                  </div>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>False. With bip9-based soft-fork-based activation of
              segwit, miner blocks will not be orphaned unless they are
              intentionally segwit-invalid (which they currently are
              not). If you have told miners otherwise, let me know.</div>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
    A reasonable miner automatically checks every transaction seen, to
    see if it might be valid with his own outputs substituted.<br>
    <br>
  </body>
</html>