From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A1C351532 for ; Tue, 22 Sep 2015 17:45:02 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E32EC8E for ; Tue, 22 Sep 2015 17:45:01 +0000 (UTC) Received: by wicfx3 with SMTP id fx3so35386946wic.0 for ; Tue, 22 Sep 2015 10:45:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2ORlj6PEsrVhooTlE4t8t3lkiJccKUZ8mtg8R6FuI4A=; b=Qcm24lRaHeYWCBQ0zEYkYPLQrYsxBWyfiT9LnQrPzkDuhpyL/gw5hFFquvAIwKY5nA lrLeP70Tno7z67RGaW7thoR8otfXPYDzPgCSR+kol2mKuU5281RF43Z6ZoVXwL7e6xDt sFBYi+bR83ZZymDh/rmejXseI6/mxoQ2gm5EPsA+bvwHM0HSW33gP4ve05/BQWHs2Tsj PMXXSj10QSOaaE9yFeIq8S99VijQkVz1f8rH/4g4k2aqj5dh+/evKdMKMCEUVZSFD5iR BDZjmJF8UXGQ1q1i0O1OZ2SoxbT2cdNAaZ0a6ApuC0gTBv3khE6AmAHLsWkLdUh0qNCD M5sA== X-Gm-Message-State: ALoCoQnvpTLEqE5RjfkcB1XYt8YdGedMGQ2ABki4CSxJzKBXO48wYmdIcgYw8N8Ui2hzwP1pts+v MIME-Version: 1.0 X-Received: by 10.180.182.7 with SMTP id ea7mr22492569wic.58.1442943900363; Tue, 22 Sep 2015 10:45:00 -0700 (PDT) Received: by 10.194.37.5 with HTTP; Tue, 22 Sep 2015 10:45:00 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 Sep 2015 19:45:00 +0200 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: Peter Todd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: =?UTF-8?Q?Jorge_Tim=C3=B3n_via_bitcoin=2Ddev?= 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: Tue, 22 Sep 2015 17:45:02 -0000 On Fri, Sep 18, 2015 at 12:44 AM, Peter Todd wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > > > On 17 September 2015 12:14:38 GMT-07:00, "Jorge Tim=C3=B3n via bitcoin-de= v" 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. That would work. I was thinking about requiring OP_MATURITY 100 (or greater than 100) in all the scriptPubKey's of the expiry transaction.