From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <pete@petertodd.org>) id 1XZU1B-0002Me-3s for bitcoin-development@lists.sourceforge.net; Thu, 02 Oct 2014 00:13:13 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.148.108 as permitted sender) client-ip=62.13.148.108; envelope-from=pete@petertodd.org; helo=outmail148108.authsmtp.net; Received: from outmail148108.authsmtp.net ([62.13.148.108]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XZU1A-00054Y-22 for bitcoin-development@lists.sourceforge.net; Thu, 02 Oct 2014 00:13:13 +0000 Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s920D5eM060409; Thu, 2 Oct 2014 01:13:05 +0100 (BST) Received: from [25.162.121.21] ([24.114.45.134]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s920CxFE091888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Oct 2014 01:13:00 +0100 (BST) User-Agent: K-9 Mail for Android In-Reply-To: <CABsx9T1Wh1ypQ-RCkAh+1qEw7QvBnuPja1teJ6xq9F_gQHAGOA@mail.gmail.com> References: <20141001130826.GM28710@savin.petertodd.org> <201410011823.56441.luke@dashjr.org> <CABsx9T1xC_1GzquEKBH3TQscZoo3EjXyQFR3FF6BXufjduL_JA@mail.gmail.com> <542C6C61.30301@gmail.com> <CABsx9T1Wh1ypQ-RCkAh+1qEw7QvBnuPja1teJ6xq9F_gQHAGOA@mail.gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Peter Todd <pete@petertodd.org> Date: Wed, 01 Oct 2014 17:12:51 -0700 To: Gavin Andresen <gavinandresen@gmail.com>, Alan Reiner <etotheipi@gmail.com> Message-ID: <72667BA8-FDE6-4C6B-A463-9DFAE067C287@petertodd.org> X-Server-Quench: df7c3eeb-49c8-11e4-9f74-002590a135d3 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdgAUF1YAAgsB AmIbW1VeUV57WWI7 aQ5PbARZfE5LQQRp VFdNRFdNFUsrCB4B dVZoJxl7dg1OcDB5 bEJmECQNWxd5IBMv X0pdRmUbZGY1bH0W BkdcagNUcgZDfk5E aVUrVz1vNG8XDQg5 AwQ0PjZ0MThBJSBS WgQAK04nCXUhPwZ0 SwoLEykaVWYlag4Q CzsNCWI9OWsvH38T H2ppHBogKRIMBwtC V0gFHD9eOkVJSTAs CEtQUE8YH3VGWSpa HlU1JANJBnRbXGJV FFNEURgTCiRDGDVJ TTs1 X-Authentic-SMTP: 61633532353630.1024:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 24.114.45.134/465 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1XZU1A-00054Y-22 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> 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: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Thu, 02 Oct 2014 00:13:13 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 1 October 2014 14:34:33 GMT-07:00, Gavin Andresen <gavinandresen@gmail.com> wrote: >On Wed, Oct 1, 2014 at 5:04 PM, Alan Reiner <etotheipi@gmail.com> >wrote: >No, the burner would supply the funding transaction plus the redeeming >script as the proof-of-burn to whoever needed the proof. No, the redeemScript has to be provably published to miners for the sacrifice to be valid; if not you can exploit the scheme by hiding the redeemScript and having a big miner mine it at lower-than-face-value cost when it unlocks. >Only after at least one confirmation, if there was some risk that >revealing >the redeeming script would make miners refuse to mine that first >transaction because they want to get it plus the CHECK TIME BLOCK VERIFY >"burn" >transaction. Yes, you could do that in a followup tx containing the redeemScript in an OP_RETURN output to prove publication. That said as I said to Luke-Jr, the sacrifices need to unlock pretty far into the future, so I don't see miners bothering to do this. -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQFQBAEBCAA6BQJULJiDMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8 cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhTwKCACD+GWzID7Qhn2no1p9 KYNiYlQVNt+DPZY0QB7MujL8riAmyJBliF9zptfjEdvglShoIzonJien/DOCjp9S Lw2wMvPhtZGgSttJEvlr3wclty6TfWygd4Y+v/MR8TnYC99su7HhiQ1pkqohkklv RxeF9jXhcJMERzN6wPUyeowfziBAfbWw+M5CwiXRlzLLBWO37eoDTXzUD0Np5Nia nFxQ7sAsSbLijVpvigh9uIi3/1347VqwMc+0ZsZoZ2AnMICA8Q+XKNHv7DKpChxw Xa+P532Di34uu8dlG/Z/UwYdENvb15P1yUZ7CEDfqNqrZp0RM7x+XKMA7QPwhuz3 YSBp =mvKP -----END PGP SIGNATURE-----