1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id A1C351532
for <bitcoin-dev@lists.linuxfoundation.org>;
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 <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 22 Sep 2015 17:45:01 +0000 (UTC)
Received: by wicfx3 with SMTP id fx3so35386946wic.0
for <bitcoin-dev@lists.linuxfoundation.org>;
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: <C9A1D16E-03F7-4860-8E9B-32A98E06CE49@petertodd.org>
References: <a50b82c156c805a284386d80a42cc926@xbt.hk>
<CAOG=w-vGqsAcw5vdY8SaGVe4Q6XX1J=GCsZftWgjES_N_5c2pA@mail.gmail.com>
<CABm2gDp_afyqskEV8QmO43=-6R_2OJm36GVQxcQO_3ao2jC1gw@mail.gmail.com>
<C9A1D16E-03F7-4860-8E9B-32A98E06CE49@petertodd.org>
Date: Tue, 22 Sep 2015 19:45:00 +0200
Message-ID: <CABm2gDrqLf_YmG9BtxfANkfbXpA_7sm79ZoG5cJHog0a2O=4BA@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Peter Todd <pete@petertodd.org>
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?=
<bitcoin-dev@lists.linuxfoundation.org>
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2015 17:45:02 -0000
On Fri, Sep 18, 2015 at 12:44 AM, Peter Todd <pete@petertodd.org> 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" <bitcoin-dev@lists.linuxfoundation.org> 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.
|
