Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XZR4k-0005aR-Mh for bitcoin-development@lists.sourceforge.net; Wed, 01 Oct 2014 21:04:42 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.173 as permitted sender) client-ip=209.85.216.173; envelope-from=etotheipi@gmail.com; helo=mail-qc0-f173.google.com; Received: from mail-qc0-f173.google.com ([209.85.216.173]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XZR4j-0000u7-Tx for bitcoin-development@lists.sourceforge.net; Wed, 01 Oct 2014 21:04:42 +0000 Received: by mail-qc0-f173.google.com with SMTP id x13so1181686qcv.32 for ; Wed, 01 Oct 2014 14:04:36 -0700 (PDT) X-Received: by 10.224.75.9 with SMTP id w9mr54257216qaj.32.1412197476470; Wed, 01 Oct 2014 14:04:36 -0700 (PDT) Received: from [192.168.1.85] (c-69-143-221-64.hsd1.md.comcast.net. [69.143.221.64]) by mx.google.com with ESMTPSA id c7sm1615622qam.8.2014.10.01.14.04.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Oct 2014 14:04:36 -0700 (PDT) Message-ID: <542C6C61.30301@gmail.com> Date: Wed, 01 Oct 2014 17:04:33 -0400 From: Alan Reiner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <20141001130826.GM28710@savin.petertodd.org> <201410011823.56441.luke@dashjr.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.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 (etotheipi[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1XZR4j-0000u7-Tx 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 21:04:43 -0000 On 10/01/2014 04:58 PM, Gavin Andresen wrote: > 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). If you're doing some kind of proof-of-burn scheme, wouldn't using P2SH defeat the purpose of it?