Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id F12061197 for ; Thu, 17 Sep 2015 22:48:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail148093.authsmtp.net (outmail148093.authsmtp.net [62.13.148.93]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 3A38221A for ; Thu, 17 Sep 2015 22:48:05 +0000 (UTC) Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt16.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t8HMlxGO055245; Thu, 17 Sep 2015 23:47:59 +0100 (BST) Received: from [26.114.152.68] ([172.56.42.19]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t8HMljIo027735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Sep 2015 23:47:51 +0100 (BST) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Peter Todd Date: Thu, 17 Sep 2015 22:44:05 +0000 To: =?ISO-8859-1?Q?Jorge_Tim=F3n?= , =?ISO-8859-1?Q?Jorge_Tim=F3n_via_bitcoin-dev?= , Mark Message-ID: X-Server-Quench: 24134ec1-5d8e-11e5-9f76-002590a135d3 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR bgdMdwUUC1AEAgsB AmMbWVdeVFp7XGQ7 ag1TcwBbfE5MQQRj T0xPR01TWkFgeWFd XGdBUht1cAZDNnZ0 ZUYsXHRaX0AvJkdg RxpcQHAHZDJldWlJ V0ZFdwNWdQpKLx5G bwR8GhFYa3VsNCMk FAgyOXU9MCtqYApU RgVIKkhXQkcPGnYg XRkEBjwkAUwCQU0A X-Authentic-SMTP: 61633532353630.1024:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 172.56.42.19/465 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Fill-or-kill transaction X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 22:48:06 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 17 September 2015 12:14:38 GMT-07:00, "Jorge Timón via bitcoin-dev" wrote: >Fill or kill us normally used for trades and I think it can be >confusing. >Previous times this has been discussed it has been discussed under >nExpiryTime or op_height (which enables expiration), for example, in >the >freimarkets white paper. > >As Mark points out this can be made safe by requiring that all the >outputs >of a transaction that can expire have op_maturity/csv/rcltv of 100. >That >makes them as reorg-safe as coinbase transactions. Unfortunately this >doesn't play very well with p2sh... Why wouldn't that work with p2sh? It can be implemented by a "treat like Coinbase" flag in the UTXO set, set when the output is created. -----BEGIN PGP SIGNATURE----- iQE9BAEBCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV+0Ip AAoJEMCF8hzn9Lncz4MIAIQpz7tKbmjEuETX6BnPatJ50I+kS6CQ4eE+e1irXpbb OCMe0A2TGzw9G5t7DgMU1lCcbcbuqOxMOrHYXuGsGkpVtRrLFbkS/F9vCS2RJT0w kRkL2ecN8riAjh1lUUgY1CEgVyhkwh6Rw1ZALu3Ba2tISysMfXjAW1GiLHlgxP7g xD6zS0OTTokG/7+s1hGK2Nd4q/ZHnfOO1JgiBzrykGNq4enp7nRhiZKhnc/0ILJA 3WAsAMI14ZUxs95onjey7J3100tZBetYr14jzLRvf+w1klBNSvcen9dr+VhdyXYk MPMOwuUtq4OI1vt3HDoMjNFT6olg0gTxzWe8Grn96S4= =pP3Q -----END PGP SIGNATURE-----