From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XZQyx-0005FB-7q for bitcoin-development@lists.sourceforge.net; Wed, 01 Oct 2014 20:58:43 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.171 as permitted sender) client-ip=209.85.160.171; envelope-from=gavinandresen@gmail.com; helo=mail-yk0-f171.google.com; Received: from mail-yk0-f171.google.com ([209.85.160.171]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XZQyv-0005ix-K9 for bitcoin-development@lists.sourceforge.net; Wed, 01 Oct 2014 20:58:43 +0000 Received: by mail-yk0-f171.google.com with SMTP id 79so382121ykr.16 for ; Wed, 01 Oct 2014 13:58:35 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.0.226 with SMTP id 62mr16129139yhb.115.1412197114990; Wed, 01 Oct 2014 13:58:34 -0700 (PDT) Received: by 10.170.188.23 with HTTP; Wed, 1 Oct 2014 13:58:34 -0700 (PDT) In-Reply-To: <201410011823.56441.luke@dashjr.org> References: <20141001130826.GM28710@savin.petertodd.org> <201410011823.56441.luke@dashjr.org> Date: Wed, 1 Oct 2014 16:58:34 -0400 Message-ID: From: Gavin Andresen To: Luke Dashjr Content-Type: multipart/alternative; boundary=089e01634b40645944050462c317 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XZQyv-0005ix-K9 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] [BIP draft] CHECKLOCKTIMEVERIFY - Prevent a txout from being spent until an expiration time X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 20:58:43 -0000 --089e01634b40645944050462c317 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Oct 1, 2014 at 2:23 PM, Luke Dashjr wrote: > houghts on some way to have the stack item be incremented by the height at > which the scriptPubKey was in a block? A limitation of encoding the target > height/time directly, is that miners may choose not to mine the first > transaction until they can also take the "burn to fee". > If the first transaction is P2SH, then the miner won't know there is an advantage to holding it until it is too late (the scriptPubKey is an opaque hash until the second transaction is final and relayed/broadcast). -- -- Gavin Andresen --089e01634b40645944050462c317 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On W= ed, Oct 1, 2014 at 2:23 PM, Luke Dashjr <luke@dashjr.org> wrot= e:
houghts on some way to have the stack item be incremen= ted by the height at
which the scriptPubKey was in a block? A limitation of encoding the target<= br> height/time directly, is that miners may choose not to mine the first
transaction until they can also take the "burn to fee".

If the first transaction is P2SH, then the miner won= 9;t know there is an advantage to holding it until it is too late (the scri= ptPubKey is an opaque hash until the second transaction is final and relaye= d/broadcast).


--
--
Gavin Andresen
--089e01634b40645944050462c317--