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 1XF5Ar-0000ug-H6 for bitcoin-development@lists.sourceforge.net; Wed, 06 Aug 2014 17:38:53 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.148.96 as permitted sender) client-ip=62.13.148.96; envelope-from=pete@petertodd.org; helo=outmail148096.authsmtp.net; Received: from outmail148096.authsmtp.net ([62.13.148.96]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XF5Aq-0001ox-DD for bitcoin-development@lists.sourceforge.net; Wed, 06 Aug 2014 17:38:53 +0000 Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s76HckmJ084235; Wed, 6 Aug 2014 18:38:46 +0100 (BST) Received: from [25.186.101.212] ([24.114.23.154]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s76HcbEI005421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Aug 2014 18:38:41 +0100 (BST) User-Agent: K-9 Mail for Android In-Reply-To: <53E26434.2070502@monetize.io> References: <53E1A8AF.4030206@thinlink.com> <53E23F49.3020605@thinlink.com> <63a80796-609e-43f5-9280-4cd8cf5d2648@email.android.com> <53E25F8A.5070905@thinlink.com> <53E26434.2070502@monetize.io> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Peter Todd Date: Wed, 06 Aug 2014 10:34:21 -0700 To: Mark Friedenbach , Tom Harding , Bitcoin Dev Message-ID: X-Server-Quench: 82ef99ca-1d90-11e4-9f74-002590a135d3 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdgQUGUATAgsB AmIbWlxeU1V7XWA7 aQ5PbARZfEhNQQRv VFdNRFdNFUsrBhp5 VUxrKxlycgFEeTBx ZU5iWj5TXhEsfE8u E1NVQWQGeGZhPWQC WRZfcx5UcAFPdx8U a1N6AHBDAzANdhES HhM4ODE3eDlSNilR RRkIIFQOdA4HEyIx XRUDGzQ0AUwODzkp Jho9I1UAHUEXekgi KVo7UE4ZNBl6 X-Authentic-SMTP: 61633532353630.1024:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 24.114.23.154/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: 1XF5Aq-0001ox-DD Subject: Re: [Bitcoin-development] deterministic transaction expiration 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, 06 Aug 2014 17:38:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 6 August 2014 10:21:56 GMT-07:00, Mark Friedenbach wrote: >On 08/06/2014 01:02 PM, Tom Harding wrote: >> 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. > >Note that this would be a massive, *massive* change that would >completely break bitcoin output frangibility. Merchants would have to >start demanding input history back to a certain depth in order to >ensure >they are not exposing themselves to undue reorg-expiry risk. Bitcoin is already "broken" in that regard due to malleability, and more fundamentally, the existence of anyone-can-spend outputs, known private keys, SIGHASH_ANYONECANPAY, etc. In any case, reorg-doublespend risk is no different than reorg-expiry risk. -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQFQBAEBCAA6BQJT4mcdMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8 cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhSdiB/9no/fXR50Zej4l6Hyt gDvM9GWosGxZydQfplrUYzS9nLWTJgkjNYkrJk1OXPlkiNoHhlpCK6TuEL3DXBo8 txDBhp/xls7aFHELpPhP5iKrEj0J6fyMp9wKRVtUu0J+RhHY22v+iEQf//dGUX4v hQPwATubmnyeVd71TAKyW6zCPjoEh0IG19tRVvw/v7/qNTXHdSZTkSVzQa4GP2gr 2xVqXTeOycPKqIU+GaNI4aRAL2DUm1kW3jG/+h3BwnJNd5q+0ELpC6xDmkA6hkNz N6BFCtoghhKNH+FNsZKAzE9w8dYngZQbaA9vVdaR6SXzz9KuG526EymOF7e55IBJ FMu+ =ii2+ -----END PGP SIGNATURE-----