<div dir="ltr">That won&#39;t necessarily work through large reorgs.  You don&#39;t want to create a situation where a miner cannot mine a previously mined transactions.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">

On Wed, Aug 6, 2014 at 1:02 PM, Tom Harding <span dir="ltr">&lt;<a href="mailto:tomh@thinlink.com" target="_blank">tomh@thinlink.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <br>
    Today we have first-eligible-height (nLockTime), and mempool
    expiration measured from this height would work for the goals being
    discussed, no fork or protocol rev.<br>
    <br>
    With first-eligible-height and last-eligible-height, creator could
    choose a lifetime shorter than the max,  and in addition, lock the
    whole thing until some point in the future.<div><div class="h5"><br>
    <br>
    <br>
    <div>On 8/6/2014 9:15 AM, Jeff Garzik wrote:<br>
    </div>
    </div></div><blockquote type="cite"><div><div class="h5">
      <div dir="ltr">A fork is not necessarily required, if you are
        talking about information that deals primarily with
        pre-consensus mempool behavior.  You can make a &quot;network TX&quot;
        with some information that is digitally signed, yet discarded
        before it reaches miners.<br>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Wed, Aug 6, 2014 at 11:42 AM, Peter
          Todd <span dir="ltr">&lt;<a href="mailto:pete@petertodd.org" target="_blank">pete@petertodd.org</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN
            PGP SIGNED MESSAGE-----<br>
            Hash: SHA256<br>
            <div><br>
              <br>
              <br>
              On 6 August 2014 08:17:02 GMT-07:00, Christian Decker &lt;<a href="mailto:decker.christian@gmail.com" target="_blank">decker.christian@gmail.com</a>&gt;
              wrote:<br>
              &gt;+1 for the new field, overloading fields with new
              meaning is definitely<br>
              &gt;not<br>
              &gt;a good idea.<br>
              <br>
            </div>
            To add a new field the best way to do it is create a new,
            parallel, tx format where fields are committed by merkle
            radix tree in an extensible and provable way. You&#39;d then
            commit to that tree with a mandatory OP_RETURN output in the
            last txout, or with a new merkle root.<br>
            <br>
            Changing the tx format itself in a hard-fork is needlessly
            disruptive, and in this case, wastes opportunities for
            improvement.<br>
            -----BEGIN PGP SIGNATURE-----<br>
            Version: APG v1.1.1<br>
            <br>
iQFQBAEBCAA6BQJT4kzQMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8<br>
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhamzCAC+zRaXRodP63+ke3K+<br>
Viapiepvk4uIOlqxqtMB2O0zWcyu2+xCJDiRPykK/6HLDBeFDEC9/dGK8++Lovl6<br>
//qZ340LOPFlgT2kYy9E5h/yX469fhtsWhBCv2K47fWwkMS0S/0r4SQnCkbt2R2c<br>
4dQjkoldhw6rNMBTUmwvhSlL30KsT/msWTZiX7DW/YjfOzezEJzy+mYyKp9Sk7ba<br>
1fOiBXORk7mNOs7sTYTvje3sqEGpGTOLP08cY/RCEvl6bG8mHkPqwiojq+3biHFP<br>
RsoBVu1f5cbnU7Wq0gPNdVnQssnEQDadyTX8gT0Wze7PuVyaZT2mXFZBKzSHuLy2<br>
            sJKN<br>
            =oPSo<br>
            -----END PGP SIGNATURE-----<br>
            <br>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <br>
        -- <br>
        Jeff Garzik<br>
        Bitcoin core developer and open source evangelist<br>
        BitPay, Inc.      <a href="https://bitpay.com/" target="_blank">https://bitpay.com/</a>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><div class=""><pre>------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
<a href="http://pubads.g.doubleclick.net/gampad/clk?id=153845071&amp;iu=/4140/ostg.clktrk" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=153845071&amp;iu=/4140/ostg.clktrk</a></pre>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
Bitcoin-development mailing list
<a href="mailto:Bitcoin-development@lists.sourceforge.net" target="_blank">Bitcoin-development@lists.sourceforge.net</a>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a>
</pre>
    </div></blockquote>
    <br>
  </div>

<br>------------------------------------------------------------------------------<br>
Infragistics Professional<br>
Build stunning WinForms apps today!<br>
Reboot your WinForms applications with our WinForms controls.<br>
Build a bridge from your legacy apps to the future.<br>
<a href="http://pubads.g.doubleclick.net/gampad/clk?id=153845071&amp;iu=/4140/ostg.clktrk" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=153845071&amp;iu=/4140/ostg.clktrk</a><br>_______________________________________________<br>


Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Jeff Garzik<br>Bitcoin core developer and open source evangelist<br>BitPay, Inc.      <a href="https://bitpay.com/" target="_blank">https://bitpay.com/</a>
</div>